On Tuesdayen den 30 July 2002 13.31, Pixel wrote: > Oden Eriksson <[EMAIL PROTECTED]> writes: > > > > After I got sick of allways needing to re-make my ramdisk to include > > > > modules of my choice when installing a new kernel, I made these small > > > > changes that I hope will be included in the next initscripts package. > > > > (thanks in advance...) > > > > > > why exactly do you need a special module? > > > > Because of lots of reasons, and because it's easy and possible with this > > small patch. > > that's not enough. Since you need it, someone else may need it and we > may be able to do it more automagically that telling to edit > /etc/sysconfig/installkernel
For example I would like to load my md raid from the ramdisk so I _never_ lose that in case of a bad upgrade/kernel/module/whatever. The logic is now only that "/" is used to determine what fs and its approriate modules is needed, right?. I have an md at "/var/qmail/queue" and "/home". If I would remove the md for "/home" no md modules would make it into the ramdisk. Another example is that I _ALLWAYS_ have the loop module in my ramdisk... (guess why:-)) > > It would also be very useful if the mkinitrd script itself could make use > > of the "INITRDOPTS" value... If this was working we didn't have to > > re-make the ramdisk for our very own special needs. > > agreed The "INITRDOPTS" value would override any (well some?) voodoo magic misfortunes, and that's a good thing IMHO. Also, as I come to think of it, this will increase boot time since the module(s) never has to be checked and uncompressed. Neat. -- Regards // Oden Eriksson Deserve-IT Networks -> http://d-srv.com
