UpgradingHowto

From TrustixWiki

Jump to: navigation, search

This is how you should upgrade from old releases to new releases

Contents

[edit]

Common rules

  • Do backups - This is the most important rule before any upgrade
  • Set up a temporary alternative - This is essential for anyone upgrading a production server.
  • Use swup if possible - Although you can upgrade your server using the installation CD, it's not the best solution.
  • Test a lot before you deploy the upgraded server.
  • If you run into trouble like services failing to start, compare the original config file with the new one provided by the upgraded RPM. The new files have the .rpmnew extension. Often new versions require new paramters in the config file.


[edit]

Upgrade from TSL 1.x to 2.2

Back up your configuration and user data and do a complete reinstall. This is the fastest and most successful path.

Some people have used swup for this, although it will most likely break, and should not be done on production systems.


[edit]

Upgrade from TSL 2.1 to 2.2

(taken from a posting of CHT in tsl-discuss (http://lists.trustix.org/pipermail/tsl-discuss/2004-November/012424.html

This might also work for 2.0 to 2.2.

If you are using PostgreSQL please have a look at PostgreSQL prior to the upgrade

  • Back up important data, including config files.
  • Remove the contrib areas from your swup config, as upgrades including contrib packages tend to break: 
vi /etc/swup/swup.conf
  • Enable kernel upgrade and activation (Unless you use a custom kernel): 
vi /etc/sysconfig/bootloader
(Change from AUTOACTIVATE=no to AUTOACTIVATE=yes)
vi /etc/swup/swup.conf
(Change from exclude_pkg_regexp = "kernel.*" to exclude_pkg_regexp = "")
  • Find out what non-official packages you have installed: 
swup --list-alien
(The point is to have these in the back of your mind if you run into problems later on. It might be wise to 
remove them if such problems occurs.)
  • modify /etc/swup/swup.conf urls to point to trustix /pub/trustix/releases/trustix-2.2/ 
vi /etc/swup/swup.conf
  • Make sure the cache is clean: 
swup --flush-cache
  • You are now ready to upgrade your system. First we check what will be updated: 
swup --upgrade --poll-only
(Take time to find out if you like the result. If swup is to be upgraded, it will only list itself and some 
dependencies.)
  • Now do the real upgrade: 
swup --upgrade
(If something breaks, then removing the alien packages might be a good idea.. )
  • After upgrade, you should always check if some packages have been abandoned in the new version: 
swup --list-alien
(Remember that some of the aliens might be available in the community contrib section.)
  • Now you may reintroduce the contrib area: 
vi /etc/swup/swup.conf
  • And perform an upgrade of those, if any: 
swup --upgrade
  • Now is the time to reboot your system: 
reboot
[edit]

Upgrade from TSL 2.X to 3.0

Please back up your configuration and user data and do a complete reinstall. This is the fastest and most successful path.

Some people have used swup for this, although it will most likely break, and should not be done on production systems.

[edit]

Upgrade from TSL 3.0 to 3.0.X

Retrieved from "http://www.trustix.org/wiki/index.php/UpgradingHowto"
Personal tools