[PATCH] hald coldstart device mapper fix v1

[David Zeuthen]

On Sat, 2005-03-12 at 21:33 -0600, W. Michael Petullo wrote:
> Hald's coldplug code currently creates hotplug events for device mapper
> devices too early.  These events should be postponed until after all
> other block devices have been processed.  This allows hald to assign a
> parent to a device mapper device.
> 
> The attached patch addresses this issue.  In addition, this patch replaces
> occurences of "sesame" with "luks."  Hald now expects LUKS devices to
> be named like this:
> 
> /dev/mapper/luks_crypto_eb59030f-de81-4ae7-9628-2f4dfc852970
> 
> instead of this:
> 
> /dev/mapper/sesame_crypto_eb59030f-de81-4ae7-9628-2f4dfc852970
> 

I've now committed this, thanks. So, it luks :-) like the main thing
we're needing now is the ability for g-v-m to call into hald with the
method Setup(string in passphrase) on the interface
org.freedesktop.Hal.Device.Volume.Crypto on the hal device object
representing the crypted block device. This should then trigger a small
script that invokes cryptsetup and we should be in business, yeah?

(note also that cryptsetup-luks is now in Fedora Rawhide, thanks to Bill
Nottingham)

Cheers,
David

> _______________________________________________
> hal mailing list
> hal at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/hal

_______________________________________________
hal mailing list
hal at lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/hal