[Petter Reinholdtsen] > This patch change this to be the case, and make sure the two scripts > are started in the order cryptdisk-early, cryptdisk, and stopped in > the opposite order even when dependency based boot sequencing is > used.
On second thought, and to reduce the complexity of initscripts while making cryptsetup more self contained, I recommend using a reverse dependency on checkfs in init.d/cryptdisk, to replace an optional dependency in checkfs on cryptdisk. Here is the updated patch: diff -ur cryptsetup-1.0.6~pre1.orig/debian/cryptdisks.init cryptsetup-1.0.6~pre1/debian/cryptdisks.init --- cryptsetup-1.0.6~pre1.orig/debian/cryptdisks.init 2008-01-03 20:45:47.000000000 +0100 +++ cryptsetup-1.0.6~pre1/debian/cryptdisks.init 2008-01-04 01:07:18.000000000 +0100 @@ -1,10 +1,11 @@ #! /bin/sh ### BEGIN INIT INFO # Provides: cryptdisks -# Required-Start: checkroot -# Required-Stop: umountroot +# Required-Start: checkroot cryptdisk-early +# Required-Stop: umountroot cryptdisk-early # Should-Start: udev devfsd raid2 mdadm lvm evms # Should-Stop: udev devfsd raid2 mdadm lvm evms +# X-Start-Before: checkfs # Default-Start: S # Default-Stop: 0 6 # Short-Description: Setup remaining encrypted block devices. I will drop the cryptdisks depend from checkfs soon, so it would be great if this reverse depend could make it to unstable quickly. Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
