© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
f33e652
(Get the code!)
Well, the problem is exacltly defined.
But if devkit-disks/udisks create the mapping in reaction of inserting device event, it should also handle removal of device.
Maybe I can add some --force option to cryptsetup, which remove all existing (or dead) crypt mapping of previous instance of newly appeared device.
But cryptsetup cannot handle
- force unmounting possible FS (it is another level, cryptsetup have no idea about FS)
- trigger any event on device removal (cryptsetup is just binary to create mapping, someone must add some rule which run it - here udisks I guess?)
I am reassigning this to udisks, but there is probably some part where cryptsetup can help, not sure. Please let me know if you have such request...