Hi. Regarding the bug itself.
It seems that the initramfs-script simply misuses the root= kernel parameter. AFAIK, the device specified at root= is simply the "finalised" device where the root-filesystem itself is found. So e.g. /dev/sda1 if it's directly on it,.. or /dev/vg00/lv00 if it's directly on lv00,... I think lvm2 should do the following (at least regarding initramfs-images): - The hook script should check, whether the root-fs as specified in fstab is directly or indirectly on an LV (guess it's quite complex to really find that out). If so,.. it includes /sbin/lvm - The boot script, should first check if /sbin/lvm is there,... and if so, unconditionally to lvm vgchange -an I guess the init-script should still scan, as further devices may have appeared. Cheers, Chris. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
