On Wed, 2010-06-02 at 11:20 -0700, Timothy Renner wrote: > On Wed, Jun 2, 2010 at 7:51 AM, Brian Long <[email protected]> wrote: > > On 06/01/2010 01:51 PM, Timothy Renner wrote: > >> I am looking to find a way to get a module added to the initrd > >> automatically, whenever mkinitrd is invoked. I can use the --with > >> flag to force a module in, but if for some reason the ramdisk is > >> automatically rebuilt (The Driver Update process) or if somebody > >> manually re-runs mkinitrd, it will no longer be included and our > >> system will no longer boot. It looks like /etc/modprobe.conf or > >> /etc/modprobe.d is useful for SCSI modules only. Is there any other > >> configuration file that can be used to tell mkinitrd to automatically > >> include *any* arbitrary module? > > > > Tim, > > mkinitrd is just a shell script so you can view it. At the top, it > > sources files in /etc/sysconfig/mkinitrd/ and it appears that if you > > define "MODULES=foobar", it will include foobar in the initrd. It sets > > $CONFMODS to $MODULES and lower in the script it runs findmodule against > > each module listed in $CONFMODS. > > > > I've not tested this, but it appears it would work. > > Excellent... That's exactly what I was looking for. Tested and > working. Thank you very much Brian. > > Also found in testing: Since all these files are sourced, it should be: > > MODULES="$MODULES foo bar baz" > > so an earlier definition isn't wiped out.
Right. This does work, though it might impact supportability if you are e.g. replacing the existing root filesystem in the initrd. Would you mind sharing some more detail about the module concerned in the case that there is an issue with the initrd in general? (if this is a custom hack, then cool, but I'm interested if it's a general workaround). Jon. _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
