SLUG Mailing List Archives
Re: [SLUG] WAS FC5 Kernel headers
- To: Howard Lowndes <lannet@xxxxxxxxxxxxx>
- Subject: Re: [SLUG] WAS FC5 Kernel headers
- From: O Plameras <oscarp@xxxxxxxxxxx>
- Date: Tue, 04 Apr 2006 12:04:16 +1000
- Cc: slug@xxxxxxxxxxx
- User-agent: Thunderbird 1.5 (X11/20060313)
Howard Lowndes wrote:
I don't think it is a bug, at least not on the part of Fedora. The
headers, specifically usb-drivers in usb.h, appear to have been
changed and the various third party drivers haven't cought up and thus
are no longer compatible.
I agree on this.
FC4 has glibc-2.3.X whereas FC5 has glibc-2.4.X, a major upgrade.
Upgrade is removing before installing, and many services
that are not activated yet at that time of removing will break.
I got problems when trying to upgrade via the Internet using 'YUM'.
'YUM' is unable to remember and keep track as to what to remove
and then install first and next so as not to break the services that are
required. YUM as I understand it is not designed to do major
upgrades only upgrades within the same versions.
The way I got around this was I upgraded 'udev' first.
This is the key point.
Upgrading udev removes glibc-2.3.X and friends and installed
And since glibc and friends are the basic building blocks of apps,
modules, and kernel in Linux and with 'udev' in place I was OK even if
I may have broken others down the chain. The services that are broken
down the chain were re-installed using 'YUM'.
Summary of my upgrading experience with FC4 to FC5 using yum:
I backup my important data (This is no hassle as I use OpenAFS.
Everything is backup/replicated automatically as the system was
being used. This includes local and remote data. As I was fighting
with FC4 to FC5 upgrades users could continue to use the
network as normal and without interruptions. This is for another
Step 1. rpm -Uvh \
Step 2. yum -y update udev
Step 3. yum -y update kernel
Step 4. reboot
Step 5. yum -y update
Any dependency problems, I yum -y remove <problem-package>
and yum re-install.
Disclaimer: No warranty that these procedures will work for anyone.
It should be pointed out that upgrading locally using CDROM has no problems.
Hope this helps.