Difference between revisions of "Installing/Upgrading"
From GalliumOS Wiki
| Line 1: | Line 1: | ||
| − | |||
| − | + | == Upgrading within a Major Release (e.g. 2.0 to 2.1)== | |
| − | |||
| − | |||
| − | + | Run GalliumOS Update: | |
| − | We | + | * '''GalliumOS Update''' from the launcher menu, or |
| + | * <code>galliumos-update</code> from a command line | ||
| + | |||
| + | == Upgrading to a New Major Release (e.g. 2.1 to 3.0)== | ||
| + | |||
| + | There are two methods: | ||
| + | |||
| + | * '''Back up user data and reinstall''' (Recommended!) This is quick, safe, gives you a fresh clean install, and always works. | ||
| + | * '''Upgrade in-place''' (NOT Recommended!) Shortly after final release of a new major version, we will release an in-place upgrader script, named something like <code>galliumos-upgrade-2to3</code>. Again, this is '''not''' the recommended approach! | ||
| + | |||
| + | === Why Not Upgrade-in-Place? === | ||
| + | |||
| + | The upgrade-in-place script attempts to carefully update your package sources to the new repositories, download the new packages, and install them. | ||
| + | |||
| + | This ''usually'' works, but it takes a long time, pulls down a lot of data from the net, requires 2-3GB of free disk space, can leave you with a mixture of old and new system data, and sometimes fails in awkward ways. | ||
| + | |||
| + | We strongly recommend that if you choose this path, you make sure all of your user data is backed up first. And then -- since you already have a backup of user data -- we strongly recommend that you choose the '''Reinstall''' method instead. | ||
Latest revision as of 13:38, 9 July 2019
Upgrading within a Major Release (e.g. 2.0 to 2.1)
Run GalliumOS Update:
- GalliumOS Update from the launcher menu, or
-
galliumos-updatefrom a command line
Upgrading to a New Major Release (e.g. 2.1 to 3.0)
There are two methods:
- Back up user data and reinstall (Recommended!) This is quick, safe, gives you a fresh clean install, and always works.
- Upgrade in-place (NOT Recommended!) Shortly after final release of a new major version, we will release an in-place upgrader script, named something like
galliumos-upgrade-2to3. Again, this is not the recommended approach!
Why Not Upgrade-in-Place?
The upgrade-in-place script attempts to carefully update your package sources to the new repositories, download the new packages, and install them.
This usually works, but it takes a long time, pulls down a lot of data from the net, requires 2-3GB of free disk space, can leave you with a mixture of old and new system data, and sometimes fails in awkward ways.
We strongly recommend that if you choose this path, you make sure all of your user data is backed up first. And then -- since you already have a backup of user data -- we strongly recommend that you choose the Reinstall method instead.
