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: > >On Tue, 2008-07-01 at 23:11 +0200, David Härdeman wrote: > >> On Tue, Jul 01, 2008 at 09:09:19PM +0100, Scott James Remnant wrote: > >> >We already have a loop in mountroot() to deal with this problem, it > >> >waits until the root device is actually available before proceeeding. > >> > >> Which is after all initramfs scripts have already had their chance of > >> executing. > >> > >No initramfs script should use the root device before it has been > >mounted. > > > >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... > What does it create it from?
If it creates it from block devices, it should be written as a script called by a udev rule, not as an initramfs script. 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. This is one of a number of major differences between Ubuntu and Debian. Scott -- Scott James Remnant [EMAIL PROTECTED]
signature.asc
Description: This is a digitally signed message part
