Package: cryptsetup Version: 2:1.1.2-1 Hello,
while examining differences in the legacy and dependency-based boot-sequence in order to decide whether I'd probably like to switch away from legacy I've stumbled over cryptdisk-early. The legacy boot-sequence for mdadm, cryptsetup and lvm in rcS given from the postinst update-rc.d sequence numbers is: S25mdadm-raid S26cryptdisks-early S26lvm2 S27cryptdisks However, cryptdisks-early ships a LSB hint # X-Start-Before: mdadm-raid lvm2 which I understand as it would be started before mdadm-raid. And, indeed, /sbin/insserv -vn 2>&1 | grep ' enable ' | grep rcS.d | sed -e 's/^.* -> //' -e s%init.d/../%% | sort | egrep '(crypt|mdadm|lvm)' reveals S09cryptdisks-early S10mdadm-raid S11lvm2 S12cryptdisks on my system, i.e. cryptdisks-early would really be started before mdadm-raid using dependency-based boot. This makes a huge difference for me since I'm stacking raid -> crypt -> lvm and thus need some crypt-init between raid and lvm. The current dependency-based boot-sequence doesn't offer this to me while the legacy boot-sequence does. I'm not really sure what's the intended boot-sequence but I personally think the legacy one makes more sense than the new dependency-based one (ymmv). I'm not sure if such differences would justify a higher severity. regards Mario -- [mod_nessus for iauth] <delta> "scanning your system...found depreciated OS...found hole...installing new OS...please reboot and reconnect now"
signature.asc
Description: Digital signature