Am 03.04.2013 19:02, schrieb Lennart Poettering: > On Wed, 03.04.13 17:02, Harald Hoyer (har...@redhat.com) wrote: > >>> Well, this explanation is too short. You need to clarify that this only >>> has an effect on devices listed in fstab with their device mapper path >>> (i.e. rather than LABEL= or UUID=, which is by far more common). For the >>> generic case there is no way around setting x-systemd.device-timeout=0 >>> in fstab, because we wouldn't know that the fs with that label or uuid >>> is hidden behind a certain encrypted device before we have decrypted >>> it. >> >> This is not true. This also affects LVM on top of the cryptsetup devices, >> where >> none of the /dev/mapper devices is and can be in /etc/fstab. > > Well, LVM does not care about proper dependencies. They still are so > naive to assume they are run at a point in time where all devices are > probed.
That is untrue. LVM can be enabled entirely from udev if it is so configured. > Whether or not .device units exist is pretty much ignored by LVM. That's true, LVM cannot hook into systemd,
signature.asc
Description: OpenPGP digital signature
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
