https://bugzilla.novell.com/show_bug.cgi?id=463161
User tilman.vogel@web.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=463161#c16
Tilman Vogel changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|WONTFIX |
--- Comment #16 from Tilman Vogel 2009-02-25 08:07:49 MST ---
Hm, I understand that this cannot be fixed for 10.3 -> 11.1 but for future
releases, the migration from existing 10.3 installations will still produce
this problem.
The main flaw of "trying to migrate" is that it produces a configuration that
is definitely defective and which will produce corrupted home directories.
(Too bad, I didn't save the fsck output from fixing mine. It didn't look nice!
And data was lost.)
I propose to resolve this bug by either
(a) changing the migration logic to:
- take the new vanilla config file and only migrate the volume definitions
- inform the user that advanced configuration options were not migrated and
where to find the old config file (rpmsave)
Of course, this is not failsafe either, because volume definitions from
advanced configs may not work or work incorrectly when plugged into the vanilla
config file. But at least it is not obviously wrong.
(b) fixing the mount.crypt script such that an invocation via mount does not
result in defective behaviour, see my original comment #8. This would render
the migrated config file well-behaving. I prefer this option.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.