HAL and LUKS II: revenge of cryptsetup

[David Zeuthen]

On Mon, 2008-04-21 at 15:48 +0100, Sam Morris wrote:
> I gave this a go but couldn't get it to work. The uevents sent by the
> kernel don't contain any device-mapper specific information, so that's
> why I had to resort to the two workarounds I mentioned, neither of which
> would work. But it's possible (probable!) that I just don't know the
> correct udev-fu to make udev aware of the mapping name...

I think that you could probably run dmsetup to figure out the name...
FWIW, there are some patches that adds an 'export' command to dmsetup so
things are imported into the environment and as such will be made
available in the udev database. There's an open bug about this in the RH
bugzilla to get this upstream [1]

https://bugzilla.redhat.com/show_bug.cgi?id=438604

Anyway, all the device mapper stuff is kinda a mess right now and I
guess you're just caught with seeing races as a result of this. With
time it will get sorted.

     David

[1] : before some people start flaming me for using the RH bugzilla:
couldn't find any upstream bug tracker for device mapper and RH is the
main device mapper developer anyway