Upgrading from FC6 to Fedora 7 with yum

Now that Fedora 7 has been release it is time to upgrade from that crusty old Fedora Core 6. Note that they have removed the “Core” from the name so a few things have changed with the paths used in yum. Last year I did a post on how to upgrade from FC5 to FC6 and this upgrade happened on the first box I used for that.

  1. Before you start see the note after these steps about checking for disk labels
  2. yum update
  3. yum clean all
  4. I repeated update and clean all a second time to make sure everything got updated
  5. I then ran the command:
    rpm -Uhv
  6. I then found that I had to move fedora-development.repo and fedora-updates.repo out of /etc/yum.repos.d/ and replace them with fedora-development.repo.rpmnew and fedora-updates.repo.rpmnew. I also needed to remove a custom repo I had but no longer used so I didn’t take time to figure out why it needed to be removed.
  7. I then did a yum -y update and waited
  8. After a good wait another X server was started so you may think about not doing the update while running under X. Luckily it was able to start on another console so all was ok. Now it was time for a reboot.
  9. After the reboot I had to fix up some NVidia issues but overall it looks like it upgraded without a problem

Notes on disk labels:

There are a few things listed in the release notes under Upgrade Related Issues.

The first was to make sure all your drives have labels. You can do this by running the command “/sbin/blkid” and then checking that each line that is not part of the LVM system has a LABEL entry. If you need to add a label to a drive use the “/sbin/e2label” command and then edit your /etc/fstab to use the label on boot instead of the device.

LABEL=/boot             /boot                   ext3    defaults        1 2

You don’t need to label LVM drives since the LVM keeps track of the drives it uses on its own. The only drive I had on a stock install that wasn’t under the LVM was /boot and it had a label already.

After you upgrade they sugest running the following command and then upgrading anything that has a date before the upgrade date:

rpm -qa –last > RPMS_by_Install_Time.txt
Please follow and like us:
About shk

shk is a DevOps engineer with more than 12 years of experience in different organizations. He enthusiastic about learning new technologies and shares his knowledge through his blogs.

Comment Policy:

Your words are your own, so be nice and helpful if you can. Please, only use your real name, not your business name or keywords. Using business name or keywords instead of your real name will lead to the comment being deleted. Anonymous commenting is not allowed either. Limit the amount of links submitted in your comment. We accept clean XHTML in comments, but don't overdo it please.

Tell us what you're thinking...

All comments are moderated.

* Denotes required field.



Previous Post:
Next Post: