noinitrd

Quote:

Originally Posted by bassmadrigal(Post 6259972)WILL YOU STOP PUTTING WORDS IN MY MOUTH? You've been doing this a lot lately and I really don't appreciate it. I did NOT and never have advocated for no initrd on Slackware. Seriously, learn to read my posts. I'm trying to learn here and I don't appreciate you ignoring my post and pretending that I'm saying you're wrong. I am asking why you think Slackware was being held back by not automatically generating an initrd and what "progress" can be accomplished since it is doing it now? I already provided several examples of when initrds are *needed* and you have now showed me one example of being able to recover a system that was poorly updated by having an initrd. But I can recover just as easy if I keep my old kernel and entry in the bootloader or if I have a usb boot setup. Having an initrd in the case you provided is one of many ways to recover the system I don't really see how this is the big "progress" you're preaching. I'll quote your line again that I was asking the original question about: What progress was made by automatically generating an initrd with the installer? Why do you believe that defaulting to huge was holding back Slackware?

I prefer to not use an initrd if possible, but in some cases I need one, so it's good to have the option to add one ;)

Having some experience with user generated boot and kernel issues, I personally find it way easier to fix those if there is not an initrd involved.