Template:Upgrading Alpine executeupgradescript: Difference between revisions
(Removing 'lbu ci' from upgradescript notes) |
m (Use Cmd template) |
||
| Line 1: | Line 1: | ||
== Execute upgrade script == | == Execute upgrade script == | ||
The new media has a 'upgrade' script found on root level on media. This 'upgrade' script needs to be executed and walked through. | The new media has a 'upgrade' script found on root level on media. This 'upgrade' script needs to be executed and walked through. | ||
{{Cmd|/media/$LBU_MEDIA/upgrade}} | |||
You will be informed about various changes and you will be able to choose if you want to keep your old config-files or if you want to use a new.<BR> | You will be informed about various changes and you will be able to choose if you want to keep your old config-files or if you want to use a new.<BR> | ||
Revision as of 10:22, 26 July 2010
Execute upgrade script
The new media has a 'upgrade' script found on root level on media. This 'upgrade' script needs to be executed and walked through.
/media/$LBU_MEDIA/upgrade
You will be informed about various changes and you will be able to choose if you want to keep your old config-files or if you want to use a new.
Each setup is different, so it's hard to say what needs to be upgraded and what should be kept.
When the new media holds a updated version of configfile, you will be prompted with something that looks like this:
Quit, Next, Show diff, Edit new, Zap new, Use new (q/n/s/e/z/u) [s]:
If you choose to 'Edit new' you will use the 'vi' editor.
A short note on how you use that editor:
- i = Enter "insert" mode so you can edit the content
- [esc] = Enter CMD-mode where you can chose to save/quit
- CMD-mode has these options
- :w = Write your changes
- :q = Quit editor
- :q! = Force quit even if you have changes that is still not saved
- CMD-mode has these options