This one is straight out of the FAQ´s on the Scientific Linux website (under documentation) and is certainly not my doing, but I figured it is a bit buried and not everybody might have found it. And it´s a cheap way of adding content to this blog. As it goes simply updating your say 5.4 installation does not automatically bring you to 5.5. To get the full next point release a few additional steps are required. And with Redhat having recently released RHEL 5.6 the corresponding SL release will soon be upon us, although for the moment it looks like they are busy enough getting SL6 ready.
I have used this a few months ago to upgrade my SL 5.4 Live CD x86_64 install to 5.5, just as detailed below, and it works perfectly. If you´re upgrading from anything more recent than 5.2 you won´t need to perform the steps relating to perl and gaim below, indeed you may not even have gaim installed.
DO NOT FORGET TO SUBSTITUTE 5x IN THE EXAMPLES BELOW WITH WHATEVER RELEASE YOU WANT TO UPGRADE TO, AND TO SUBSTITUTE i386 WITH x86_64 IF YOU HAVE A 64-BIT SYSTEM.
For The Impatient
I have used this a few months ago to upgrade my SL 5.4 Live CD x86_64 install to 5.5, just as detailed below, and it works perfectly. If you´re upgrading from anything more recent than 5.2 you won´t need to perform the steps relating to perl and gaim below, indeed you may not even have gaim installed.
"It is not required that administrators upgrade their release, because the security errata will be updated for all releases. But there are often features and/or packages included in later releases that were not available with the earlier releases.
Below the steps, for yum to change to the latest 5.x release.
These instructions are for updating between minor releases, such as from 5.0 to 5.1. Changes between major releases 4 and 5 (such as from 4.2 to 5.1), cannot be done with yum, but must be done with the main installer."
DO NOT FORGET TO SUBSTITUTE 5x IN THE EXAMPLES BELOW WITH WHATEVER RELEASE YOU WANT TO UPGRADE TO, AND TO SUBSTITUTE i386 WITH x86_64 IF YOU HAVE A 64-BIT SYSTEM.
For The Impatient
- x86_64 only yum remove perl.i386 gaim.i386 gaim-devel.i386
- yum clean all
- rpm -Uvh ftp://ftp.scientificlinux.org/linux/scientific/5x/i386/misc/RPMS/yum-conf-latest.SL.noarch.rpm
- yum update yum
- yum update
- Make sure you have done your backup's.
I haven't heard of anyone needing them, but don't you be the first. - Make sure you have enough disk space. In particular, make sure you have enough space in /var/cache, which is where yum downloads the rpms.
- x86_64 only yum remove perl.i386 gaim.i386 gaim-devel.i386
In earlier versions of SL (5.0, 5.1 & 5.2) there was a i386 version of perl and gaim in the x86_64 release. This was taken out by the upstream version, and eventually out of SL. In order to update to newer versions of SL, you need to take the i386 version of perl and gaim out of your x86_64 install. - optional yum update
This will get your system up to date with the latest packages. It will also make the last step smaller. - yum clean all
This cleans up all the headers and packages from your old yum configuration. If you do not do this step, it is very likely that yum will say that there is nothing to do. - rpm -Uvh ftp://ftp.scientificlinux.org/linux/scientific/5x/i386/misc/RPMS/yum-conf-latest.SL.noarch.rpm
This will install the latest yum.conf for your system. If you customized your yum.cron, or your yum.cron.excludes files, these will not be touched. - yum update yum
It's always good to have the latest yum before doing this, just incase the latest yum has fixed some bug you would have run into. - yum update
This is the big part, where everything gets changed. - Check your grub settings. Although yum usually get's things right when it updates kernels, it is always a good idea to give the grub config file a check.
- optional yum clean all
This cleans up all the rpms that you just downloaded, clearing up your disk space. - /sbin/reboot
Reboot into your new kernel and Scientific Linux release
No comments:
Post a Comment
Please leave your comment here. Spam will be deleted.
Note: only a member of this blog may post a comment.