| Summary: | Preserve UUID when recreating file systems | ||
|---|---|---|---|
| Product: | [Applications] partitionmanager | Reporter: | Volker Lanz <vl> |
| Component: | general | Assignee: | Volker Lanz <vl> |
| Status: | CONFIRMED --- | ||
| Severity: | wishlist | ||
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Unspecified | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Volker Lanz
2009-07-10 20:13:47 UTC
This is trivial, but not as trivial as it might seem, because the FileSystem implementations right now _create_ UUIDs in their respective updateUUID() methods. First step would be to separate generation of new UUIDs and writing them to disk. The updateUUID() methods should just write the contents of the m_UUID prop and nothing else. Copying the UUID from the old to the new file system should probably be done when creating the copy, not in some op or job implementation; this has the advantage of showing the (old and new) correct UUID in the preview before applying. |