BUG in crypsetup-1.0.6

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi all,

Gentoo ships with cryptsetup 1.0.6. This version introduced a call to udevsettle, which got 'corrected' to a call to udevadm. As far as I can see, this is supposed to avoid a race condition.

What I am interested in is, which race condition that exactly is, and what exactly cryptsetup still needs to do after that point.

I am asking since udev is not the only hotplugging mechanism. Personally I feel that calling a specific external program is just not the right way, to handle something like that.

For my usage case busybox is used together with busybox' mdev, thus a call to udevsettle (or udevadm for that matter) is pretty much pointless.

Regards

-Sven

---------------------------------------------------------------------
dm-crypt mailing list - http://www.saout.de/misc/dm-crypt/
To unsubscribe, e-mail: dm-crypt-unsubscribe@xxxxxxxx
For additional commands, e-mail: dm-crypt-help@xxxxxxxx


[Index of Archives]     [Device Mapper Devel]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Packaging]     [Fedora SELinux]     [Yosemite News]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux