IT/Software/Upgrading Between Versions: Difference between revisions
Jump to navigation
Jump to search
Access restrictions were established for this page. If you see this message, you have no access to this page.
Walttheboss (talk | contribs) |
Walttheboss (talk | contribs) |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
== General == | ==General== | ||
Though you can upgrade every 6 months there is often little reason to do this in a production environment. | Though you can upgrade every 6 months there is often little reason to do this in a production environment. | ||
Every two years a LTS(Long Term Support) release comes out. | Every two years a LTS(Long Term Support) release comes out. | ||
* It is supported for 5 years. | *It is supported for 5 years. | ||
* It does get point releases and kernel upgrades. | *It does get point releases and kernel upgrades. | ||
* Most software can be brought to a current version with a ppa | *Most software can be brought to a current version with a ppa | ||
<br /> | Common Thoughts | ||
* We generally try to tweak a server as little as possible. | |||
** Staying in line with common practice help us get help when needed. | |||
* As you upgrade make notes of what config files have changed. | |||
** Choose the Package Maintainer's version. | |||
*** New features have likely been added. | |||
** It usually keeps a copy of the old one. | |||
* | |||
==Check== | |||
<br /><code>sudo do-release-upgrade -c</code> | |||
The c is obviously for check | The c is obviously for check | ||
== Upgrade == | ==Upgrade== | ||
<code>sudo do-release-upgrade</code> | <code>sudo do-release-upgrade</code> | ||
This normally only works after the point release is out. | This normally only works after the point release is out. | ||
You can force it sooner with the -d flag at the end | You can force it sooner with the -d flag at the end | ||
<code>sudo do-release-upgrade -d</code> | <code>sudo do-release-upgrade -d</code> | ||
The upgrade path from 16.04 to 18.04 was bad. | |||
The upgrade path from 18.04 to 20.04.1 was great. | |||
*You may need to purge a ppa or two for it to work. | |||
*We recommend y-ppa manager | |||
Latest revision as of 08:42, 17 December 2020
General
Though you can upgrade every 6 months there is often little reason to do this in a production environment.
Every two years a LTS(Long Term Support) release comes out.
- It is supported for 5 years.
- It does get point releases and kernel upgrades.
- Most software can be brought to a current version with a ppa
Common Thoughts
- We generally try to tweak a server as little as possible.
- Staying in line with common practice help us get help when needed.
- As you upgrade make notes of what config files have changed.
- Choose the Package Maintainer's version.
- New features have likely been added.
- It usually keeps a copy of the old one.
- Choose the Package Maintainer's version.
Check
sudo do-release-upgrade -c
The c is obviously for check
Upgrade
sudo do-release-upgrade
This normally only works after the point release is out.
You can force it sooner with the -d flag at the end
sudo do-release-upgrade -d
The upgrade path from 16.04 to 18.04 was bad.
The upgrade path from 18.04 to 20.04.1 was great.
- You may need to purge a ppa or two for it to work.
- We recommend y-ppa manager