Bug#272079: initrd-tools: creation of initrd image fails when lvm is compiled statically into kernel
Package: initrd-tools
Version: 0.1.74
Severity: normal
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?
Cheers,
Jörg
-- System Information:
Debian Release: 3.1
APT prefers experimental
APT policy: (990, 'experimental'), (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.8.1-ck7
Locale: LANG=sv_SE.UTF-8, LC_CTYPE=sv_SE.UTF-8
Versions of packages initrd-tools depends on:
ii coreutils [fileutils] 5.2.1-2 The GNU core utilities
ii cpio 2.5-1.1 GNU cpio -- a program to manage ar
ii cramfsprogs 1.1-6 Tools for CramFs (Compressed ROM F
ii dash 0.5.1-3 The Debian Almquist Shell
ii util-linux 2.12-7 Miscellaneous system utilities
-- no debconf information
Reply to: