Comment 50 for bug 428435
Revision history for this message
| Martin Pitt (pitti) wrote Re: luks encrypted partition not detected or mounted automatically | #50 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
We discussed that in #ubuntu-release. Given how close karmic's release is, we think this is a viable strategy:
(1) For karmic, patch blkid to prefer luks over ext*
Rationale: This has been the behaviour for years, and worked well. We also know that creating a luks volume did not properly clean up traces from a previous ext file system, while we know that creating an ext file system over a luks file system worked properly. (I'll verify that again, though)
Reopening an util-linux task for that.
(2) For Lucid, discuss a proper migration strategy to clean up superblocks on upgrades. This isn't release critical for Karmic any more then.
Keeping non-karmic cryptsetup task for that.