LUKS code and new method interface

[W. Michael Petullo]

[...]
 
> I was thinking it might make sense to ship this in the hal tarball so
> distros only need to ship cryptsetup-luks? I would appreciate that.

My opinion is that the device information file and hal-luks-setup should
move into the hal project.  Everything else should remain in a separate
project.  Gnome-luks-format should definitely not go in hal.  I'm not
sure that luks-format should either.  After all, mkfs.ext2 is not in hal.

I'd be perfectly willing to hear any arguments.

[...]
 
> Ah, OK, we can do a little bit better here. Something like
> 
>   <device>
>     <match key="volume.fsusage" string="crypto">

[...]

Okay, luks-tools 0.0.6 now includes 15-storage-luks.fdi, which looks
like what you recommended.  Again, I agree that this should move into
hal's tarball.

I added the final piece to my gnome-volume-manager patch.  See [1].
The whole thing now works, though I don't yet tear down the crypto device
when the volume is unplugged.  I would really like to have a udev
pro. look at the patch.  I am sure it needs a little work and would
appreciate the chance to learn.

[1] https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=152946

-- 
Mike

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