On Mar 15, 2012, at 12:09 PM, Bruce Dubbs wrote:
> Qrux wrote:
>
>> IMO, LVM and mdraid should be done super-early (whether embedded in
>> some other script or separated into their own). It should go right
>> after modules are loaded (S05modules in rcS.d, so maybe S06LVM and
>> S06md) for the people doing fancy initramfs boots with modules.
>> Started early, udev, swap, checkfs, and mountfs could all use mdraid
>> and LVM devices.
>
> I don't see how that sort of thing could be done before devices are
> populated by udev.
Just did some quick testing. LVM should be started *after* the LFS udev
script, as pvdisplay does not see any of the physical devices before that
script is run.
It's likely more complex, since vgchange has switches that enable and disable
certain udev interactions, but that can be left for someone willing to dig
deeper who wants to fine tune the ordering. I'm certainly fine with it after
S10udev, and I'd still advocate starting LVM before S20swap.
I'm still firmly of the opinion that if LVM userspace isn't present in LFS then
it should be omitted from the lfs bootscripts, and instead, either use seds in
the LVM install (to patch what--S10udev?) or more cleanly as its own bootscript
(e.g., S15lvm2).
Q
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
