[Pkg-cryptsetup-devel] Bug#488271: cryptsetup: use a loop to wait for the root device

[David Härdeman]

On Wed, July 2, 2008 00:33, Scott James Remnant wrote:
> On Tue, 2008-07-01 at 23:44 +0200, David Härdeman wrote:
>> On Tue, Jul 01, 2008 at 10:25:50PM +0100, Scott James Remnant wrote:
>>> If you want to modify or create root devices, it should be done with a
>>> udev rule.
>>
>> Ummm, are we still talking about the same thing? cryptsetup creates the
>> root device in an initramfs script...of course it won't use any root
>> devices...
...
> If it creates it from block devices, it should be written as a script
> called by a udev rule, not as an initramfs script.

We're discussing in the context of Debian bug #488271 right now. That is,
the discussion is whether we need a proposed rootdelay patch in Debian's
version of cryptsetup or not...

> See mdadm, lvm, etc. for comparison -- in Ubuntu, those are called from
> udev, when the underlying block device is actually ready.
>
> cryptsetup should behave in the same way; when a block device is ready
> for use, it should be called by a udev rule and make the devmapper
> device -- that will release the loop in mountroot() and allow the
> initramfs to exit.

I completely agree with this approach. In fact I proposed it to Marco
d'Itri (Debian's udev maintainer) in April 2007 and pushed a testing
branch to the initramfs-tools git repo at about the same time.
Unfortunately it was rejected by the udev maintainer. I should probably
raise that proposal again when I have time...

Anyway, we're going offtopic.

-- 
David Härdeman