32 lines
1.5 KiB
Plaintext
32 lines
1.5 KiB
Plaintext
|
Welcome to the 2.0.5 -> 2.1 upgrade procedure!
|
||
|
|
|
||
|
|
It must first be said that this upgrade DOES NOT take a particularly
|
||
|
|
sophisticated approach to the upgrade problem, it being more a question
|
||
|
|
of providing what seemed "good enough" at the time. A truly polished
|
||
|
|
upgrade that deals properly with the broad spectrum of installed 2.0.5
|
||
|
|
systems would be nice to have, but until that gets written what you get is
|
||
|
|
this - the brute-force approach!
|
||
|
|
|
||
|
|
What this upgrade will attempt to do is best summarized thusly:
|
||
|
|
|
||
|
|
1. fsck and mount all file systems chosen in the label editor.
|
||
|
|
2. Ask for a location to preserve your /etc directory into and do so.
|
||
|
|
3. Extract all selected distributions on top of your existing system.
|
||
|
|
4. Copy certain obvious files back from the preserved /etc, leaving the
|
||
|
|
rest of the /etc file merge up to the user.
|
||
|
|
5. Drop user in a shell so that they may perform that merge before
|
||
|
|
rebooting into the new system.
|
||
|
|
|
||
|
|
And that's it! This "upgrade" is not going to hold your hand in all
|
||
|
|
major respects, it's simply provided to make one PART of the upgrade
|
||
|
|
easier.
|
||
|
|
|
||
|
|
IMPORTANT NOTE: What this upgrade procedure also may do, in fact, is
|
||
|
|
completely destroy your system (though much more quickly than you
|
||
|
|
would have been able to destroy it yourself) and it is simply
|
||
|
|
impossible to guarantee that this procedure's crude form of upgrade
|
||
|
|
automation will work in all cases. If you do this upgrade without
|
||
|
|
proper BACKUPS for any important data then you really must like living
|
||
|
|
life close to the edge, that's all I can say!
|
||
|
|
|