* The following procedure usually is '''not''' sufficient. Between two releases, usually major things change, so it's necessary to perform additional tasks manually such as updating/installing packages, adapting script files, etc. Altogether it may be less work to reconfigure the new andLinux installation by reinstalling your additional packages and coping your files, including all the applications' settings files (by copying all the dot-files (files whose name begin with a dot) in the home directory, you'll most probably cover all relevant settings).

== The procedure before the upgrade ==

== The procedure before the upgrade ==

-

When updating to andLinux Beta 1 (final), you'll have to run these commands:

+

When updating to andLinux Beta 2 (final), you'll have to run these commands:

* When updating from andLinux Beta 1 rc6 to andLinux Beta 1 (final), the procedure above is sufficient (as all other changes in the new version are installation related). When updating from an older version, it may be necessary to perform additional tasks such as updating/installing packages, adapting script files, etc.

Current revision

If you want to keep your customized base.drv when updating andLinux, you'll have to perform the following steps. It's easier to do it before the upgrade.

Notes

Just in case something might go wrong, it's recommended to make backup copies of base.drv (while andLinux is not running).

The following procedure usually is not sufficient. Between two releases, usually major things change, so it's necessary to perform additional tasks manually such as updating/installing packages, adapting script files, etc. Altogether it may be less work to reconfigure the new andLinux installation by reinstalling your additional packages and coping your files, including all the applications' settings files (by copying all the dot-files (files whose name begin with a dot) in the home directory, you'll most probably cover all relevant settings).

The procedure before the upgrade

When updating to andLinux Beta 2 (final), you'll have to run these commands: