[pkg-cryptsetup-devel] Bug#587224: Bug#587224: Bug#587224: cryptsetup: cryptdisks-early boot-sequence difference in legacy and dependency-based boot

[Mario 'BitKoenig' Holbe]

On Sat, Jun 26, 2010 at 06:05:22PM +0200, Jonas Meurer wrote:
> On 26/06/2010 Christoph Anton Mitterer wrote:
> > But I also think, that we should keep for compatibility the older order.
> agreed, next upload will restore old order.

While you are at it, and since I don't know what exactly you did change
(this is why I don't like to open a new bug on it):

There's also a problem in the stop-sequence:
	/etc/rc0.d/K02cryptdisks
	/etc/rc0.d/K03cryptdisks-early
	/etc/rc0.d/K03umountnfs.sh
	/etc/rc0.d/K04umountfs
	/etc/rc0.d/K05lvm2
	/etc/rc0.d/K06mdadm-raid
	/etc/rc0.d/K06umountroot

vs. legacy:
	/etc/rc0.d/S31umountnfs.sh
	/etc/rc0.d/S40umountfs
	/etc/rc0.d/S49cryptdisks
	/etc/rc0.d/S50lvm2
	/etc/rc0.d/S59cryptdisks-early
	/etc/rc0.d/S60mdadm-raid
	/etc/rc0.d/S60umountroot


Both, cryptdisks and cryptdisks-early should Required-Stop: umountfs at
least, and cryptdisks-early should probably additionally X-Stop-After
(if such a thing exists): lvm2


regards
   Mario
-- 
A promise to a woman is just a lie that hasn't happened yet.
                                               -- Mr. Floppy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 482 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-cryptsetup-devel/attachments/20100705/4f52c5d8/attachment.pgp>