Red Hat Bugzilla – Bug 242463
mkinitrd checks only modules.conf.
Last modified: 2011-07-27 14:00:24 EDT
Description of problem:
The mkinitrd script will only check the modules.conf file for needed modules. If
this file has includes defined they WONT be checked. Also if a modprobe.d
directory exists it WONT be checked
Version-Release number of selected component (if applicable):
use includes in the modprobe.conf or use modprobe.d
scsi_hostadapter entries in the included files or modprobe.d files aren't
included in the created initrd.
That the listed modules are included in the new initrd
I want to implement this myself, but i need some info about the functionality
and the expected behavior.
like: check modprobe.d only when modprobe.conf doesn't exists or also when it
(In reply to comment #1)
> I want to implement this myself, but i need some info about the functionality
> and the expected behavior.
> like: check modprobe.d only when modprobe.conf doesn't exists or also when it
> exists, ...
this is the same as Fedora bz 457870, which it says was closed as of Fedora 11,
so you can grab the mkinitrd out of a Fedora 11 distribution
but i vote for backporting this from Fedora, pretty please
i'll try adding a BZ for RHEL 5