Upgrading from RedHat to Fedora 

Preparation 
remove redundant kernels 

run rpm -q kernel kernel-smp compare the results to the kernel you are running (uname -r). run 'rpm -e' for each of the kernels that you are not using ex: rpm -e kernel-2.4.22-1.2115.nptl kernel-smp-2.4.22-1.2115.nptl

Do the same with kernel-source packages.
 ex:
   rpm -e kernel-source-2.4.22-1.2174.nptl
This will make things a lot easier on you, trust me, and it frees up a HUGE
amount of disk space.
Tip !!

$ rpm -qa | grep -i kernel kernel-2.4.20-24.9 kernel-pcmcia-cs-3.1.31-13 kernel-ntfs-2.4.20-24.9 kernel-source-2.4.20-24.9

rpm -e kernel-pcmcia-cs kernel-ntfs kernel-source rm /etc/sysconfig/pcmcia.rpmsave

get your system up to date and ready for upgrade 

run the following commands:

apt-get update
apt-get install
point apt repositories to fedora core 1 

Update /etc/apt/sources.list:

# os        = Fedora Core packages
# updates   = Fedora Core updates
# stable    = Fedora.us (Extras) packages
# kspei     = Steve's random stuff (optional, mostly stuff submitted to fedora.us)
# freshrpms = freshrpms.net packages (optional, mostly desktop stuff)
rpm http://apt.kspei.com fedora/1/i386 os updates stable kspei freshrpms
rpm-src http://apt.kspei.com fedora/1/i386 os updates stable kspei freshrpms

Edit existing third-party repositories to apt configuration files in /etc/apt/sources.list.d, e.g., /etc/apt/sources.list.d/greysector.list, which is for MPlayer and some other software.

Install the "new" apt from the new distribution 
apt-get update && apt-get install apt

After the new apt is installed, the the old /etc/apt/apt.conf will be wiped out by new apt — placing only a tag saying that this is a fresh installation so that you need to choose a mirror site. /etc/apt/sources.list is also emptied.

You should make new changes ase default:

mv -f "/etc/apt/apt.conf.rpmnew" "/etc/apt/apt.conf"
mv -f "/etc/apt/sources.list.rpmnew" "/etc/apt/sources.list"
mv -f "/etc/apt/preferences.rpmnew" "/etc/apt/preferences"
Choosing your repositories for optimum downloads 

The quickest way to do this is:

apt-get mirror-select

If you don't do it, the new apt-get will ask you the same questions any way.

get GPG-signature checking ready 

see below.

Edit /etc/apt/preferences 
cat >> /etc/apt/preferences
Package: *
Pin: release c=fc1
Pin-Priority: 993
Package: *
Pin: release c=os
Pin-Priority: 992
Package: *
Pin: release c=stable
Pin-Priority: 991
Package: *
Pin: release c=at-testing
Pin-Priority: 990

This will help prevent any conflicts between the various repositories.

Upgrade the distribution 
apt-get dist-upgrade

It should work. Note that upgrading RH9->FC1 had a minor issue with some perl stuff moving around causing conflicts (Note, I didn't see anything like that going from RH 7.3 to FC1 for whatever reason). E.g., something to do with perl and perl-cgi, etc. Remove the offending packages with rpm -evv —nodeps and then continued with the upgrade by re-issuing the command "apt-get dist-upgrade".

If apt-get dist-upgrade fails, you probably just need to clean some things up manually. The simplest route is usually to just apt-get remove the offending packages.

For safety, after upgrading rpm, always run rpm —rebuilddb before doing anything else.

Upgrade the new kernel 

When all is done, the system will be basically upgraded, except for the kernel, and will still be running on the old kernel with pretty much everything else upgraded. At this point,

run apt-get dist-upgrade again. That should upgrade your kernel to the latest version and install a few things that the newer version of apt knows about (like replacing redhat-release with fedora-release).

you can say "apt-get install kernel" to install the fedora core kernel, and at a time of your choosing, you can then boot into the new kernel. The one thing I found I had to install manually was fedora-release. "apt-get install fedora-release" cleared that up.

Reboot 

Select the new kernel from the grub menu. If AOK, you should be all done. You can remove the old kernel now.

GPG-signature checking 

switch off GPG-signature checking 

To switch off GPG-signature checking with apt, edit /etc/apt/apt.conf and uncomment this line: GPG-Check "false";

Install Red Hat's gpg key. 

Some things are still signed with it instead of the Fedora key for some reason.

cd /etc/apt/gpg \
 && links -source \
   http://ftp.kspei.com/pub/redhat/linux/9/en/os/i386/RPM-GPG-KEY \
   > gpg-pubkey-db42a60e-37ea5438

The next time you run apt, it will import that and any other files that begin with 'gpg-pubkey-' in /etc/apt/gpg. See /usr/lib/apt/scripts/gpg-import.lua.

Be sure to grab the keys for any other repository you use (e.g. freshrpms, my "kspei" stuff, rpm.livna.org, etc.).

Log 

% apt-get remove mozilla mozilla-mail mozilla-nss mozilla-psm xchat

% apt-get -f install mjpegtools mjpegtools-libs
Reading Package Lists... Done
Building Dependency Tree... Done
The following NEW packages will be installed:
  mjpegtools mjpegtools-libs
0 upgraded, 2 newly installed, 0 removed and 12 not upgraded.
Need to get 0B/838kB of archives.
After unpacking 1856kB of additional disk space will be used.
Committing changes...
Preparing...                ########################################### [100%]
        file /usr/lib/liblavfile-1.6.so.0 conflicts between attempted installs of mjpegtools-1.6.2-7.rhfc1.at and mjpegtools-libs-1.6.1-0.lvn.6.1
        file /usr/lib/liblavjpeg-1.6.so.0 conflicts between attempted installs of mjpegtools-1.6.2-7.rhfc1.at and mjpegtools-libs-1.6.1-0.lvn.6.1
        file /usr/lib/liblavplay-1.6.so.0 conflicts between attempted installs of mjpegtools-1.6.2-7.rhfc1.at and mjpegtools-libs-1.6.1-0.lvn.6.1
        file /usr/lib/liblavrec-1.6.so.0 conflicts between attempted installs of mjpegtools-1.6.2-7.rhfc1.at and mjpegtools-libs-1.6.1-0.lvn.6.1
E: Error while running transaction

apt-get remove transcode perl-Video-DVDRip
  -- solve the above mjpegtools/mjpegtools-libs problem

apt-get remove lm_sensors
rpm -ev --nodeps mplayer perl-libwww-perl

apt-get check
E: Unmet dependencies. Try 'apt-get -f install' with no packages

Keep running:

apt-get update
apt-get upgrade
apt-get check
apt-get install

until AOK, i.e.,

% apt-get upgrade
Reading Package Lists... Done
Building Dependency Tree... Done
0 upgraded, 0 newly installed, 0 removed and 0 not upgraded.

% apt-get check
Reading Package Lists... Done
Building Dependency Tree... Done

Note that kernel was also upgraded, and I wasn't bothered by
redhat-release or fedora-release at all.

% rpm --rebuilddb

problems 

mozilla has no installation candidate 
% apt-get install mozilla
Reading Package Lists... Done
Building Dependency Tree... Done
Package mozilla has no available version, but exists in the database.
This typically means that the package was mentioned in a dependency and
never uploaded, has been obsoleted or is not available with the contents
of sources.list
E: Package mozilla has no installation candidate
apt-get update
% apt-get install mozilla

— ok now.

An extra kernel-BOOT 
% rpmqi kernel
kernel-2.4.20-24.9
kernel-BOOT-2.4.22-1.2190.nptl_49.rhfc1.at
kernel-2.4.22-1.2190.nptl_49.rhfc1.at

kernel-BOOT:

This package includes a trimmed down version of the Linux kernel. This kernel is used on the installation boot disks only and should not be used for an installed system, as many features in this kernel are turned off because of the size constraints of floppy disks.

rpm -e kernel-BOOT

documented on: 2004.06.16

fc1 apt warning 

Newsgroups:  gmane.linux.freshrpms.user
Date:        Mon, 21 Jun 2004 18:08:52 -0400
> I think this started after the latest apt-get package was installed.
> apt-0.5.15cnc6-0.1.fc1.fr

Yes, same here.

> I get this error:
> ---
> W: There are multiple versions of "gpg-pubkey" in your system.
> [...]
> way. However, I think normal behavior would be to have more than one
> kernel installed and numerous gpg-keys.

Yes, There got to be multi gpg-pubkey packages.

> I was wondering why this warning suddenly
> started appearing when I run apt (happens on 2 computers). Is something
> wrong? Or is this the intended behavior?

The reason is (based on my obervation) that the old /etc/apt/apt.conf suddenly get wiped out by new apt — placing only a tag saying that this is a fresh installation so that you need to choose a mirror site. — I think this should be considered a bug.

Look into it (/etc/apt/apt.conf) and incorparate the new change into /etc/apt/apt.conf.rpmnew, which is saved altomatically for you. then copy it back. — This is how I solve the problem.

tong

fc1 apt warning 

> > [...]
> > The reason is (based on my obervation) that the old /etc/apt/apt.conf
> > suddenly get wiped out by new apt -- placing only a tag saying that this
> > is a fresh installation so that you need to choose a mirror site. -- I
> > think this should be considered a bug.
> > [...]
>
> You are absolutely correct. I just put the apt.conf.rpmnew as apt.conf
> and after looking at the conf files it makes sense. T

Just for the archive, fiddling with apt.conf is not enough. Now, I think all the following 3 steps are necessary.

mv -f "/etc/apt/apt.conf.rpmnew" "/etc/apt/apt.conf"
mv -f "/etc/apt/sources.list.rpmnew" "/etc/apt/sources.list"
mv -f "/etc/apt/preferences.rpmnew" "/etc/apt/preferences"

tong

fc1 apt warning 

>  mv -f "/etc/apt/apt.conf.rpmnew" "/etc/apt/apt.conf"
>  mv -f "/etc/apt/sources.list.rpmnew" "/etc/apt/sources.list"
>  mv -f "/etc/apt/preferences.rpmnew" "/etc/apt/preferences"

In general not. If you've never changed any of these files, this would be fine (but I think in that case rpm would just overwrite them). Most likely you'll need to merge your changes with whatever the new defaults are. It's fiddly, but it's the least worst alternative. I'd scream like hell if my changes got overwritten. If ever rpm tells you it's created a .rpmnew or .rpmsave file it's time to use an editor and your own judgement.

Chris

upgrading to Fedora Core 1 with apt 

http://www.silug.org/lists/silug-discuss/200405/msg00000.html

To: silug-discuss@silug.org, luci-discuss@luci.org
Date: Sun, 2 May 2004 01:18:49 -0500

Since Fedora Core 2 will be out in a couple of weeks, the plan is for Red Hat Linux 9 to be EOL'd, which means everybody still running Red Hat 9 (or earlier) needs to make a choice now… Upgrade to Fedora Core 1 (or 2, but if you are running RH9, I assume you aren't eager to try large amounts of semi-experimental software), switch to RHEL, or start pulling updates from Fedora Legacy.

Personally, I think upgrading to Fedora Core 1 is the right thing to do. It's been rock-solid for me for several months now on many systems, and upgrades from various older versions of Red Hat (7.2 through 9) have been almost 100% painless. In addition, some of the features in FC1 (like exec-shield) make it particularly appropriate for servers.

I've posted updated instructions on upgrading to FC1 here:

http://www.archlug.org/kwiki/MigratingRedHatToFedora

(I'll probably remove some of the older information from that page later. The current stuff is at the bottom — "Steve's Other Answer".)

I'd suggest checking that page for a nicely formatted (not to mention edited for corrections) copy of the instructions, but here's a copy for reference:

upgrade to fedora from shrike 

To: shrike-list redhat com
Date: Fri, 06 Feb 2004 08:43:34 -0800
> I have been using yum to update packages and everything seems to work
> ok. Also noticed that some Fedora users use a port of apt-get. What is the
> "official" package updater for Fedora? Which works best apt-get port or
> yellow dog updater?

I mucked about with yum a bit and it didn't seem to be able to figure out that it needed to use an http proxy, even though that was set in /etc/profile, as well as yum.conf. apt-get worked like a charm though, and I've been using it with great results - fills the role of up2date from my RH8/9 days.

> Someone posted that you can do a live update (dsl/cable) to fedora. Has
> anyone tried this and how?

Absolutely, I've remotely upgraded several RH8/9 boxes to fedora, and they remained up and running, and in service, the whole time (It took several hours, but as I said, I was logged into the boxes watching the upgrade process the whole time)

The basic idea is this:

  1. install apt.

  2. run the following commands to get your system up to date and ready for upgrade 

    apt-get install
apt-get update
apt-get dist-upgrade

  3. edit the /etc/apt/sources.conf to point to fedora core 1 repositories instead of RH8/9 or whatever

  4. repeat steps from #2 and watch as system is upgraded to fedora core 1

  5. I ran into a few snags where rpm complained during the upgrade about file conflicts - in every case it was something to do with perl and perl-cgi, etc. I removed the offending packages with rpm -evv —nodeps and then continued with the upgrade by re-issuing the command "apt-get dist-upgrade".

  6. When all is done, the system will be basically upgraded, except for the kernel, and will still be running on the old kernel with pretty much everything else upgraded. At this point, you can say "apt-get install kernel" to install the fedora core kernel, and at a time of your choosing, you can then boot into the new kernel. The one thing I found I had to install manually was fedora-release. "apt-get install fedora-release" cleared that up.

  7. after you're up and running on the new kernel. you'll say "wow, the debian fans had a point!" You can add a nice graphical update tool by typing "apt-get install synaptic", and then begin pointing and clicking your way to cool new programs of all sorts. 

    >  What if it fails? Linux box is gateway...

Depends on the nature of failure - possibly if you had too little disk space it would fail partway through - but barring something like that or loss of internet connection during the upgrade process, it should go just fine. In any case, it deals with problems much more gracefully than a normal install would.

Joe

Migrating from RedHat to Fedora 

http://www.archlug.org/kwiki/MigratingRedHatToFedora

Background 

Steve's Answer 

Almost.

Note I've only done this (RH 7.3 to FC 1) once, and that was on a pretty minimal install (one of my test UML boxes).
1) Change /etc/apt/sources.list 
rpm http://apt.kspei.com fedora/1/i386 os updates stable

"os" and "updates" are FC1, "stable" is fedora.us. Add other repositories as needed. (See my previous posts on installing apt on FC1.)

2) Install the "new" apt from the new distribution 
apt-get update && apt-get install apt
3) Install Red Hat's gpg key. 

Some things are still signed with it instead of the Fedora key for some reason.

cd /etc/apt/gpg \
 && links -source \
   http://ftp.kspei.com/pub/redhat/linux/9/en/os/i386/RPM-GPG-KEY \
   > gpg-pubkey-db42a60e-37ea5438

The next time you run apt, it will import that and any other files that begin with 'gpg-pubkey-' in /etc/apt/gpg. See /usr/lib/apt/scripts/gpg-import.lua.

Be sure to grab the keys for any other repository you use (e.g. freshrpms, my "kspei" stuff, rpm.livna.org, etc.).

4) Install the new kernel 
apt-get install kernel\#2.4.22-1.2129.nptl

Note: I didn't actually do this last time, so the next step just installed 2.4.22-1.2115.nptl, which I then had to upgrade, so I think this order will work better.

5) Upgrade the distribution 
apt-get dist-upgrade

It should work. Note that upgrading RH9->FC1 had a minor issue with some perl stuff moving around causing conflicts, but I didn't see anything like that going from RH 7.3 to FC1 for whatever reason.

Steve's Other Answer 

This assumes that you already have apt installed (from freshrpms, for example). Also note that this only applies to Fedora Core 1, although it should work for upgrading from just about any version of Red Hat Linux. (If you are upgrading from Red Hat 8.0, please consider just upgrading via CD. There are bugs in Red Hat 8.0's rpm that are exponentially more likely to bite you in the ass on big rpm transactions.)

  1. Update /etc/apt/sources.list: 

    # os        = Fedora Core packages
# updates   = Fedora Core updates
# stable    = Fedora.us (Extras) packages
# kspei     = Steve's random stuff (optional, mostly stuff submitted to fedora.us)
# freshrpms = freshrpms.net packages (optional, mostly desktop stuff)
rpm http://apt.kspei.com fedora/1/i386 os updates stable kspei freshrpms
rpm-src http://apt.kspei.com fedora/1/i386 os updates stable kspei freshrpms
    # Fedora Extras non-US packages (optional)
rpm http://rpm.livna.org fedora/1/i386 stable
rpm-src http://rpm.livna.org fedora/1/i386 stable
    # Macromedia Flash plug-in (optional)
rpm http://sluglug.ucsc.edu/macromedia/apt fedora/1 macromedia

  2. Create/edit /etc/apt/preferences: 

    Package: *
Pin: release c=os
Pin-Priority: 992
    Package: *
Pin: release c=stable
Pin-Priority: 991
    # This will help prevent any conflicts between the various repositories.

  3. apt-get update && apt-get dist-upgrade

    If apt-get dist-upgrade fails, you probably just need to clean some things up manually. The simplest route is usually to just apt-get remove the offending packages.

    For safety, after upgrading rpm, always run rpm —rebuilddb before doing anything else.

  4. Run apt-get update to run the mirror selector (press q since you are already using a mirror) and check for any problems. apt-get -f install should fix any problems. If not, try apt-get -f dist-upgrade, but be sure not to let apt remove anything that shouldn't be removed.

  5. The next fun thing is to update gpg keys for any of the non-Fedora repositories you want to use. 

    # My key, for the "kspei" stuff.
wget -O /etc/apt/gpg/gpg-pubkey-cf71a040-3cf27730 http://apt.kspei.com/conf/gpg-pubkey-cf71a040-3cf27730
# Freshrpms key
wget -O /etc/apt/gpg/gpg-pubkey-e42d547b-3960bdf1 http://ftp.kspei.com/pub/freshrpms/RPM-GPG-KEY
# Livna key
wget -O /etc/apt/gpg/gpg-pubkey-a109b1ec-3f6e28d5 http://rpm.livna.org/RPM-LIVNA-GPG-KEY
    apt-get will automatically install any gpg keys the next time you run it
(assuming they're in /etc/apt/gpg/ and are named gpg-pubkey-*.

  6. apt-get dist-upgrade again. That should upgrade your kernel to the latest version and install a few things that the newer version of apt knows about (like replacing redhat-release with fedora-release.

  7. Reboot. You should be all done.

documented on: 2004.06.16

Upgrading from redhat 9 to fedora - upgrade or fresh install 

http://www.linuxquestions.org/questions/archive/35/2003/11/4/119233

Hi. Is it advisable to move from redhat 9 to fedora by upgrading, or would people suggest a fresh install?

There is quite a bit of software I would prefer not to have to reinstall from scratch.

Upgrading from redhat 9 to fedora - upgrade or fresh install 

I just "upgraded" my RH8 installation to Fedora. If you choose "Upgrade" all the data and applications (in my case Gnucash) will be left intact. And only the distro is upgraded.

Hope this helps. Good luck.

inon^

Upgrading from redhat 9 to fedora - upgrade or fresh install 

Well, I always advocate for a fresh install. It wipes out any problematic files that you maybe forgot you installed. I know I am constanly trying new things and installing/uninstalling…and rpm has a nasty habit of renaming old config files which IMHO take up room I would otherwise employ. Plus, I dunno, it just seems right to me to reinstall every 3 months or so. But back up any data you want to have afterword of course. Just my .02$

Upgrading from redhat 9 to fedora - upgrade or fresh install 

I upgraded from RH9 into two of the Fedora test releases and now into FC1 and beyond.

I have not have any typical upgrade related issues, other than the inability to get the graphical boot to operate correctly (I know the correct method for enabling rbgb and how it operates in the initscripts, this is related to my video init and partitioning scheme).

I do recommend upgrade, but once you get the upgrade complete, make sure to check into programs that were available on FC1 that you didn't have from RH9. It will only upgrade what you have, and there is not package choice when upgrading. Other than this I have nothing I can say is a big issue to watch out for.

While reformatting and installing an OS, even Linux, makes a very nice clean system, it is time consuming to reconfigure your environment and isn't necessary unless you have issues you can't otherwise work around. Its always very refreshing to have it nice and cleaned out, but a whole lot of work when the benefit is low.

LordMorgul

Upgrading from redhat 9 to fedora - upgrade or fresh install 

No problems found yet after upgrading RH9.0. Really like the fonts in Mozilla. In fact I think the fonts are improved in Evolution also. Had to re-set a few settings and login to some websites, but this was painless. :cool:

Bucolic Buffalo

HOWTO: Upgrade to Fedora Core 2 - Test1, with apt 

http://fedoranews.org/ghenry/apt-fc2/

by Gavin Henry on March 08, 2004.

Warning

I am not responsible for anything that goes wrong or any damages that may occur to your system!!! And please, please, please, for the sake of your sanitiy, read this through completely, backup all your vital data, and think hard if you really want to upgrade. ;-)

Introduction: 

Well, warnings aside, let's begin.

As you all know Test1 is out and has been for a few weeks. I have waited a while for things to settle down and all the gotchas to surface, before doing an upgrade. So here is MY method of upgrading from Fedora Core 1 > Fedora Core 2 - Test1.

Option 1: Initial package upgrades: 

Download the following packages:

Then in the directory you saved them in:

rpm -Fvh *.rpm

Now, move onto "Choosing your repositories for optimum downloads:"

Option 2: Recompiling apt: 

From a mailing list post mentioned in this months newsletter, it becomes clear that you can also rebuild the apt RPM, which is the way I did it. Don't ask me why ;-)

So, grab the apt src.rpm from the official Fedora repository, and then issue:

rpmbuild --rebuild /path/to/the/rpm/apt-0.5.15cnc5-0.fdr.10.1.90.src.rpm

This will take a while depending on your setup etc.

Installing apt:

Once recompiled, simply install it with: rpm -Uvh apt*.rpm

Note: For more info about the wealth of RPM commands, see Alexandre's RPM page.

Keep an eye out for any files in /etc/apt/ with *.rpmnew extensions, as these will be from the new apt install. Move them as appropriate e.g:

mv /etc/apt/rpmpriorities /etc/apt/rpmpriorities.old
mv /etc/apt/rpmpriorities.rpmnew /etc/apt/rpmpriorities

If there are any conflicts with the apt RPM package upgrade, then simply: apt-get remove packagename Or: rpm -e packagename

Note: Keep a record of the names you remove, so that you can reinstall them later, if needed.

All that's left is adding your sources.

The first time you run apt-get nowadays, due to the nice new features, you get a text menu asking which sources you want etc., much like Debians apt. Answer the questions by hitting the right numbers, then continue ? 'c'.

Note: I had to switch off GPG-signature checking with apt, as for some reason, even after importing the Testing key, which you can download here, it didn't like the signatures. Edit /etc/apt/apt.conf and uncomment this line: GPG-Check "false";

Choosing your repositories for optimum downloads: 

The quickest way to do this is:

apt-get mirror-select

Help: We would like to find more fedora.us mirrors. So if you find any, please let me, Warren Togami or Panu Matilainen know.

I picked a good one close to the UK.

Your /etc/apt/sources.list should look something like this:

# Please choose the nearest mirror http://www.fedora.us/wiki/FedoraMirrorList

#Fedora 2 Test1 stable - Official
#rpm http://download.fedora.us fedora/fedora/1.90/i386 os stable testing unstable
#rpm-src http://download.fedora.us fedora/fedora/1.90/i386 os stable testing updates
#Fedora 2 Test1 - Spanish mirror, due to UK one slow updating.
rpm http://sunsite.rediris.es/mirror/fedora.us fedora/fedora/1.90/i386 os stable testing unstable
rpm-src http://sunsite.rediris.es/mirror/fedora.us fedora/fedora/1.90/i386 os stable testing unstable

Once you have picked a good one, issue:

apt-get update

Then:

apt-get dist-upgrade

Any duplicate packages or any other gotchas, like duplicate packages, can be handled by editing or uninstalling them ;-)

/etc/apt/apt.conf

Issuing for detailed options:

man apt.conf

My upgrade results:

When I issued a: apt-get dist-upgradeI got:

So 632mb of downloads, not bad :-). This works out to around 3hrs download time for someone on ADSL/Broadband.

Workarounds:

Commom Error:

After much heartache it appears that my router isn't fully compliant with RFCxxx standards.

After upgrading, I didn't get any external network connectivity due to the router not supporting ECN (short for Explicit Congestion Notification).

The purpose of ECN is to improve throughput on the internet by allowing individual routers to signal that they are very busy at that time. All routers should support this proposal by now and unfortunately some sites/routers still actually drop the ECN-enabled network packets.

This feature was proposed in 2001!!!.

To fix, add this into /etc/sysctl.conf net.ipv4.tcp_ecn = 0 And then either:

sysctl -p
Or:
echo 0 > /proc/sys/net/ipv4/tcp_ecn

The rest of my problems were a few package upgrade glitches, so manual upgrading of some may be required.

Fedora apt and yum repositories 

http://www.brandonhutchinson.com/Fedora_apt_and_yum_repositories.html

There are several third-party apt and yum repositories for Fedora that provide additional software not provided with Fedora Core, such as support for playing DVDs and MP3 files. Perhaps the most important consideration when choosing third-party repositories is ensuring that packages do not conflict between repositories.

My personal preference is to add the following 5 repositories to my apt and yum configuration files:

FreshRPMS http://freshrpms.net/ DAG http://dag.wieers.com/home-made/apt/ NewRPMS http://newrpms.sunsite.dk/ ATrpms http://atrpms.physik.fu-berlin.de/ Dries http://dries.studentenweb.org/apt/

Visit The Red Hat/Fedora authoritative packager list for a listing of the packages provided by the above repositories.

ATrpms lists additional RPM repositories that may be added without introducing package conflicts.

The main alternative to the third-party repositories above is to use the Fedora.us and rpm.livna.org repositories. I recommend choosing either the third-party repositories listed above or Fedora.us and rpm.livna.org. "Mixing and matching" these groups of third-party repositories could introduce package conflicts that are difficult to fix.

Upgrading Red Hat Linux/Fedora Core with yum 

http://www.brandonhutchinson.com/Upgrading_Red_Hat_Linux_with_yum.html

It is possible to upgrade your Red Hat Linux/Fedora Core system using yum instead of choosing a CD/DVD-based install or upgrade option. Only experienced Red Hat/Fedora Core users should attempt this, as the upgrade process is not necessarily seamless.

yum (Yellow dog Updater, Modified) is an excellent tool for package management. With yum, installing packages with dependencies and keeping systems up to date is easy. The tool is similar to apt for rpm and Red Hat's included up2date, although yum arguably has several advantages. In addition, yum makes upgrading between Red Hat releases relatively easy, similar to apt's dist-upgrade feature.

Theoretically, you should be able to upgrade from any Red Hat Linux/Fedora Core release to any Red Hat Linux/Fedora Core release with a yum-compatible repository (i.e. containing yum "header" files). I have successfully upgraded from Red Hat Linux 7.2 to 9, from 8.0 to 9, from 9 to Fedora Core 1, and from Fedora Core 1 to Fedora Core 2 using these steps.

The steps are slightly different when upgrading to Fedora Core releases versus a Red Hat Linux release (i.e. through Red Hat Linux 9), so the steps are presented separately.

Upgrading to Fedora Core 2 

You may want to read the following notes from the author of yum author about upgrading from Fedora Core 1 to Fedora Core 2: http://linux.duke.edu/~skvidal/misc/fc1-fc2-yum-hints.txt

Here are the steps I used to upgrade a system from Fedora Core 1 to Fedora Core 2:

  1. Install the Fedora Core 2 version of yum and fedora-release: 

    rpm -Uvh ftp://ftp.linux.ncsu.edu/pub/fedora/linux/core/2/i386/os/Fedora/RPMS/yum-2.0.7-1.1.noarch.rpm \ ftp://ftp.linux.ncsu.edu/pub/fedora/linux/core/2/i386/os/Fedora/RPMS/fedora-release-2-4.i386.rpm

  2. If yum was already installed prior to the upgrade, backup your old /etc/yum.conf file and replace /etc/yum.conf with /etc/yum.conf.rpmnew. 

    mv /etc/yum.conf /etc/yum.conf.`date +%m.%d.%y`
mv /etc/yum.conf.rpmnew /etc/yum.conf

  3. Edit /etc/yum.conf. Choose a mirror from http://fedora.redhat.com/download/mirrors.html to the [base] and [updates-released] sections. 

    Original [base] and [updates-released] sections:
    [base]
name=Fedora Core $releasever - $basearch - Base
baseurl=http://download.fedora.redhat.com/pub/fedora/linux/core/$releasever/$basearch/os/
    [updates-released]
name=Fedora Core $releasever - $basearch - Released Updates
baseurl=http://download.fedora.redhat.com/pub/fedora/linux/core/updates/$releasever/$basearch/
    New [base] and [updates-released] sections:
    [base]
name=Fedora Core $releasever - $basearch - Base
baseurl=ftp://ftp.linux.ncsu.edu/pub/fedora/linux/core/$releasever/$basearch/os/
#baseurl=http://download.fedora.redhat.com/pub/fedora/linux/core/$releasever/$basearch/os/
    [updates-released]
name=Fedora Core $releasever - $basearch - Released Updates
baseurl=ftp://ftp.linux.ncsu.edu/pub/fedora/linux/core/updates/$releasever/$basearch/
#baseurl=http://download.fedora.redhat.com/pub/fedora/linux/core/updates/$releasever/$basearch/

  4. Upgrade to Fedora Core 2. 

    yum upgrade

Upgrading to Fedora Core 1 

Here are the steps I used to upgrade a system to Fedora Core 1:

  1. Download and install the Fedora version of yum: 

    rpm -Uvh http://download.fedora.redhat.com/pub/fedora/linux/core/1/i386/os/Fedora/RPMS/yum-2.0.4-2.noarch.rpm

  2. Download and install the fedora-release package. 

    rpm -Uvh http://download.fedora.redhat.com/pub/fedora/linux/core/1/i386/os/Fedora/RPMS/fedora-release-1-3.i386.rpm

  3. Upgrade to Fedora Core 1. 

    yum upgrade

Upgrading to Red Hat Linux 9 

Here are the steps I used to upgrade a Red Hat Linux 8.0 system to Red Hat Linux 9. To upgrade to a different version, download an appropriate redhat-release package:

  1. Download and install the latest version of yum. 

    rpm -Uvh http://linux.duke.edu/projects/yum/download/2.0/yum-2.0.4-1.noarch.rpm

  2. Download and install the redhat-release package from the "new" version of Red Hat Linux. 

    rpm -Uvh ftp://ftp.quicknet.nl/pub/Linux/ftp.redhat.com/9/en/os/i386/RedHat/RPMS/redhat-release-9-3.i386.rpm

  3. Upgrade to the new release. 

    yum upgrade

The following are some problems I ran into with the upgrade from 8.0 to 9.

Problem:

Resolving dependencies
package apt needs librpm-4.1.so (not provided)
package apt needs librpmdb-4.1.so (not provided)
package apt needs librpmio-4.1.so (not provided)
package apt needs libelf.so.0 (not provided)

Solution: rpm -e apt (I will use yum instead of apt for rpm for package management; I could always manually reinstall apt for rpm after the upgrade)

Problem:

Resolving dependencies
.......identical dependency loop exceeded
package gnome-vfs2 needs gnome-mime-data >= 2.0.0-11 (not provided)

Solution: yum remove gnome-vfs2 (this will remove several packages; you may manually reinstall these after the upgrade if necessary)

Problem: after rebooting into the new kernel, my eth0 network interface was brought up with a static address and then with dhcp. During the upgrade process, the file /etc/sysconfig/network-scripts/ifcfg-eth0.dhcp was created. You may want to check /etc/sysconfig/network-scripts for any changes prior to rebooting after the upgrade.

(c) brandonhutchinson.com

Last modified: 06/03/2004

Upgrading from FC1 to FC2 using yum - a few suggestions 

http://linux.duke.edu/%7Eskvidal/misc/fc1-fc2-yum-hints.txt

There are certain things only anaconda can do. There is no other way around it. If you're using LVM stop reading and know that you must use anaconda to do this upgrade.

In general, if you're not cramped for space/time/something you should use anaconda to upgrade. You'll find you come out with a much more reliable upgrade process and much less pain. However, if you'd like to try to upgrade the whole system via yum you should follow these instructions.

Before you start it would be a good idea to do the following:

Another option for upgrading is this:
run:
 yum upgrade yum python rpm-python rpm glibc glibc-common \
             redhat-config-\* XFree86\* libxml2\*
This will upgrade a number of critical packages first and helps create a
safe(r) environment for yum to upgrade.
   After this finishes continue with the rest of the instructions.
[END OPTIONAL]

If yum appears to stall out after: Test transaction complete, Success!

That is due to a test run for diskspace. It is doing things here but nothing that reports in any meaningful way until it is done. Sorry about that. It's something I intend to correct.

After the upgrade completes you may find yum exits unhappily when it goes to make the new kernel the system default. Don't worry about this - it's not a big deal. It may or may not happen depending on how your system was patched, or not, as the case may be.

After you've finished the upgrade you should run: /usr/sbin/fix-mouse-psaux to update the system for the 2.6 kernel input layer.

Reboot your system, make sure the 2.6 kernel is selected from grub when your system boots. If it isn't you should edit your /etc/grub.conf and change the default= to point to this kernel(typically default=0)

Hope this helps, if you encounter tracebacks file them at bugzilla.redhat.com and I'll take a look.

documented on: 2004.06.16