Jörg Werner wrote:
Hi, for my firewall I build my own custom made kernels with module loading disabled for security reasons. The root volume is a LVM volume on a hardware raid. When creating the mkinitrd image, mkinitrd fails because the script tests if there is an lvm module when the root volume is on LVM. Perhaps the mkinitrd-script can also test if the module is statically compiled into the kernel?
This would be pretty difficult. Maybe some kind of --force option for mkinitrd would be helpfull? It should build an initrd even if some modules seem to be missing. Can't be worse than having a zero length initrd. Or you could simply edit /usr/sbin/mkinitrd and kick out the exit in add_modules_dep_2_5 . For the old 2.4 kernels mkinitrd ignores the error output of modprobe, so why should it die if modprobe complains for 2.6 ? Good luck Harri