I decided to upgrade from RH9 to FC1 on the weekend. Below is my experience which I thought I might share with the rest of the LUG. My system was quite heavily modified with Ximian and FreshRPMs packages for RH9. So I figured I couldn't just do a from CD "upgrade" install. The first thing I did was install yum a package manager similar to apt but for RPMs. Yum comes with FC1. I could have also installed apt for RPM too. But I was more familiar with yum. I then copied all the RPMs off the FC1 CDs I have onto my hard disk. I then downloaded the "headers" directory from the fedora core ftp server. Yum uses .hdr files to resolve dependencies. It uses headers rather than downloading the rpms because this is much more network efficient. I then configured yum to use file:/// urls to get the files off my hard disk. I then started going over my installed RPMs finding Ximain and FreshRPM versions and replacing them where Icould with FC1 versions using yum. This was an easy process of erasing the installed versions and then issuing "yum install package-name". Once I had eradicated these troublesome packages I replaced the firstboot, redhat-config-securitylevel, and lokkit packages as I read on the web they can cause install issues. Then I started manually replacing 'core' packages like glibc, basesystem, redora-release, rpm, popt etc etc. I should have also replaced libzlib, libbzip2 and others.... I learned that lesson later. :) Then issued a "yum update". This started inspecting all my packages and upgrading them. About half way though the update I had a thought, started doubting the command I had entered was doing the right thing and decided I'd stop yum with Ctrl-C, check the command and start yum again. BAD IDEA!!!! This had the effect of A) breaking yum so I couldn't use it anymore due to python errors and B) of completely hosing my RPM database. My system thought that it had installed multiple version of most of my packages. I spent the next 6 hours rebuilding my system with rpm manually. This consisted of producing a list of all installed RPMS (including dupes) and running rpm --force -Uvh on all these packages and resolving dependencies by hand. This was a painful exercise. Once that was done I did a further rpm -Fvh *.rpm in the fedora core RPMS directory. By this time yum was back to working. I then reconfigured it to use some Fedora mirrors. I also configured it to use the Fedora.us and Livna.org yum repositories. Fedora.us and livna.org have lots of extra goodies to install. I issued a "yum update" and yum began to sync up my box with all the latest package updates and also a swag of replacements for FreshRPM RPMS I had installed. My system is now in relatively good working order. But it certainly was a mission to get it there. Everything would have been soooo much easier had I resisted the temptation to Ctrl-C yum when it was working on my system in the first place. Regards -- Oliver Jones » Director » oliver.jones(a)deeperdesign.com » +64 (21) 41 2238 Deeper Design Limited » +64 (7) 377 3328 » www.deeperdesign.com
FWIW, this upgrade can go very smoothly. I've managed to do it a few times successfully now: step 0: install apt for rpm ; backup the server step 1: rpm -e all the packages I wasn't using. step 2: install the Fedora apt repositories into your /etc/apt/sources.list step 3: rpm --import http://www.fedora.us/FEDORA-GPG-KEY (can't recall if this is absolutely necessary) step 4: apt-get update && apt-get dist-upgrade step 5: ... hopefully nothing goes wrong. You may need to remove a few packages, install a few manually, and note any rpmnew files that were created. step 6: Fedora! I tried yum, and it would probably work as well. But apt just seems a bit faster, more efficient. And, FWIW, I also just recently popped a 2.6.4 kernel on a RH9 box. So far it seems to be working well. At least in a server type load. Basically following http://linuxdevices.com/articles/AT5793467888.html If you need modules: { cd /usr/src wget http://www.kernel.org/pub/linux/kernel/people/rusty/modules/module-init-tool... bzcat module-init-tools-3.0.tar.bz2 | tar x cd module-init-tools-3.0 ./configure --prefix=/ make make moveold make install ./generate-modprobe.conf /etc/modprobe.conf } { cd /usr/src wget -O - http://procps.sourceforge.net/procps-3.2.0.tar.gz | tar xz cd procps-3.2.0/ make && make install } rpm -Uvfh http://people.redhat.com/arjanv/2.6/RPMS.kernel/nfs-utils-1.0.5-1.i386.rpm echo "none /sys sysfs noauto 0 0" >> /etc/fstab mkdir /sys replace 'awk '$2 ~ /^\/$|^\/proc|^\/dev/{next}' with 'awk '$2 ~ /^\/$|^\/proc|^\/sys|^\/dev/{next}' in /etc/rc.d/init.d/halt After /proc mounting in /etc/rc.sysinit: VERSION=`uname -a | sed -e 's;.* \(2\.6\).*;\1;'` if [ "x$VERSION" = "x" ] ; then VERSION="2.4" fi if [ "x$VERSION" = "x2.6" ] ; then action $"Mounting sysfs filesystem: " mount -n -t sysfs /sys /sys fi Done the way suggested in the article you can dual boot your system with either the 2.4 or 2.6 kernel. - Peter http://rimuhosting.com ----- Original Message ----- From: Oliver Jones To: Waikato Linux Users Group Sent: Monday, March 22, 2004 11:54 AM Subject: [wlug] Upgrading from RH9 to Fedora Core 1. I decided to upgrade from RH9 to FC1 on the weekend. Below is my experience which I thought I might share with the rest of the LUG.
Yes it can go much more smoothly than my attempt. But that was my own dumb fault. Probably the easiest way to upgrade to fedora is just to do an upgrade install from the CDs. Just be sure to eradicate any custom RPMS you have installed that might conflict with those provided on the CDs first. I might have to have a play with apt. I've never really used it as I've never really had a decent play with a Debian box. Yum (and apt) is very cool. Being able to just setup "sources" and then go "yum install firefox" is very nice. And the number of useful repositories out there is growing. I just spotted one that provides a Macromedia flashplayer RPM. Now all we need is some sort of GNOME/KDE tool that takes your yum/apt sources and presents them with a nice UI for newbies/lasy people. Then you would be able to just select packages from nice detailed descriptions and have them installed. That would be nice. :) Regards On Mon, 2004-03-22 at 12:58, Peter wrote:
FWIW, this upgrade can go very smoothly. I've managed to do it a few times successfully now:
step 0: install apt for rpm ; backup the server step 1: rpm -e all the packages I wasn't using. step 2: install the Fedora apt repositories into your /etc/apt/sources.list step 3: rpm --import http://www.fedora.us/FEDORA-GPG-KEY (can't recall if this is absolutely necessary) step 4: apt-get update && apt-get dist-upgrade step 5: ... hopefully nothing goes wrong. You may need to remove a few packages, install a few manually, and note any rpmnew files that were created. step 6: Fedora!
I tried yum, and it would probably work as well. But apt just seems a bit faster, more efficient.
And, FWIW, I also just recently popped a 2.6.4 kernel on a RH9 box. So far it seems to be working well. At least in a server type load.
Basically following http://linuxdevices.com/articles/AT5793467888.html
If you need modules: { cd /usr/src wget http://www.kernel.org/pub/linux/kernel/people/rusty/modules/module-init-tool... bzcat module-init-tools-3.0.tar.bz2 | tar x cd module-init-tools-3.0 ./configure --prefix=/ make make moveold make install ./generate-modprobe.conf /etc/modprobe.conf }
{ cd /usr/src wget -O - http://procps.sourceforge.net/procps-3.2.0.tar.gz | tar xz cd procps-3.2.0/ make && make install } rpm -Uvfh http://people.redhat.com/arjanv/2.6/RPMS.kernel/nfs-utils-1.0.5-1.i386.rpm echo "none /sys sysfs noauto 0 0" >> /etc/fstab mkdir /sys replace 'awk '$2 ~ /^\/$|^\/proc|^\/dev/{next}' with 'awk '$2 ~ /^\/$|^\/proc|^\/sys|^\/dev/{next}' in /etc/rc.d/init.d/halt
After /proc mounting in /etc/rc.sysinit:
VERSION=`uname -a | sed -e 's;.* \(2\.6\).*;\1;'` if [ "x$VERSION" = "x" ] ; then VERSION="2.4" fi
if [ "x$VERSION" = "x2.6" ] ; then action $"Mounting sysfs filesystem: " mount -n -t sysfs /sys /sys fi
Done the way suggested in the article you can dual boot your system with either the 2.4 or 2.6 kernel.
- Peter http://rimuhosting.com
----- Original Message ----- From: Oliver Jones To: Waikato Linux Users Group Sent: Monday, March 22, 2004 11:54 AM Subject: [wlug] Upgrading from RH9 to Fedora Core 1.
I decided to upgrade from RH9 to FC1 on the weekend. Below is my experience which I thought I might share with the rest of the LUG. _______________________________________________ wlug mailing list wlug(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/wlug
-- Oliver Jones » Director » oliver.jones(a)deeperdesign.com » +64 (21) 41 2238 Deeper Design Limited » +64 (7) 377 3328 » www.deeperdesign.com
Oliver Jones wrote:
I might have to have a play with apt. I've never really used it as I've never really had a decent play with a Debian box. Yum (and apt) is very cool. Being able to just setup "sources" and then go "yum install firefox" is very nice
However it's not perfect. I know this is not really the fault of apt but if you have to mix'n'match sources (eg stable+backports.org) to get more up to date versions of things then sometimes you find that the install succeeds but things don't work properly. Usually this is because the dependency list for one of the packages isn't correct. eg I just upgraded to kde 3.1 from testing and then couldn't log in using kdm, the problem turned out to be that I simply needed to upgrade libpam-runtime, but it took a while to figure that out. g -- Glenn Ramsey <glenn(a)componic.co.nz> 07 8627077 http://www.componic.co.nz
Peter wrote:
If you need modules: { cd /usr/src wget
http://www.kernel.org/pub/linux/kernel/people/rusty/modules/module-init-tool s-3.0.tar.bz2
bzcat module-init-tools-3.0.tar.bz2 | tar x cd module-init-tools-3.0 ./configure --prefix=/ make make moveold make install ./generate-modprobe.conf /etc/modprobe.conf }
FYI, what Linus called module-init-tools has been packaged as a newer version of the Red Hat "modutils" package. It's availble from Arjan van de Ven's website (which you use below) in the http://people.redhat.com/~arjanv/2.6/RPMS.kernel/ dir (updates regularly; check for the latest version.) A good way to deal with this upgrade is to add the following lines to /etc/apt/sources.list rpm http://people.redhat.com arjanv/2.5 kernel rpm-src http://people.redhat.com arjanv/2.5 kernel And then apt-get dist-upgrade to get newer initscripts/LVM utils/etc. Arjan's prepackaged kernels are nice, but they enforce some Red Hat policy (no "patent concern" modules built eg. NTFS, no SMBFS - deprecated in favour of CIFS, which isn't nearly as stable), so you may well want to get his source and build your own. Some people advocate going a step further and installing kernel.org source with the Red Hat .config file, and report this fixes issues with the ATI Radeon driver. Might not be too necessary however on a server!
{ cd /usr/src wget -O - http://procps.sourceforge.net/procps-3.2.0.tar.gz | tar xz cd procps-3.2.0/ make && make install } rpm -Uvfh http://people.redhat.com/arjanv/2.6/RPMS.kernel/nfs-utils-1.0.5-1.i386.rpm echo "none /sys sysfs noauto 0 0" >> /etc/fstab mkdir /sys replace 'awk '$2 ~ /^\/$|^\/proc|^\/dev/{next}' with 'awk '$2 ~ /^\/$|^\/proc|^\/sys|^\/dev/{next}' in /etc/rc.d/init.d/halt
What's this 'replace' command'? Seems kind of useful, but isn't builtin, doesn't apt-get (on Debian) and googling for 'replace awk' doesn't help much :) Craig
participants (4)
-
Craig Box -
Glenn Ramsey -
Oliver Jones -
Peter