To upgrade GNU/Linux Fedora from core 6 to 7, then 8, there is no [really] problem today.
It was not the case when I've tried it as soon as Fedora 7 was available, but I've successfully performed such an upgrade without difficulties some days ago.
The principle is globally the same when upgrading from Fedora core N to Fedora core N+1 (see this post), or from Fedora 7 to Fedora 8 (see this post).
In addition, the recommendations of Fedora project have greatly evolved and seem now complete.
This is some additional instructions in case you have specific issues (like I had):
Update your /etc/fstab file:
It is very important to use label (LABEL=myLabel) to identity your device instead of path (/dev/xxx). The identification has changed from Fedora core 6 to Fedora 7, generally from /dev/hdX to /dev/sdY BUT there is absolutely no certainties that X and Y will equal between versions.
Using labels ensure your mount points are always the same.
Particularly it ensures your root partition (/) will be the good, and your computer will well boot after upgrade.
To update the label of a device, you can use the tune2fs command.
Upgrade from Fedora core 6 to Fedora 7:
- do not forget to clean all the yum metadata with yum clean all,
- upgrade the Fedora release:
rpm -Uhv ftp://download.fedora.redhat.com/pub/fedora/linux/releases/7/Fedora/i386/os/Fedora/fedora-release*.noarch.rpm
- upgrade your repository, for instance for livna:
rpm -Uvh http://rpm.livna.org/livna-release-7.rpm
- remove and reinstall authconfig to avoid specific issue.
Upgrade from Fedora 7 to Fedora 8:
- do not forget to clean all the yum metadata with yum clean all,
- upgrade the Fedora release:
rpm -Uvh http://mirror.anl.gov/pub/fedora/linux/releases/8/Everything/i386/os/Packages/fedora-release-*.noarch.rpm
- upgrade your repository, for instance for livna:
rpm -Uvh http://rpm.livna.org/livna-release-8.rpm
Ensure there is no dependencies problem like explained into this post.
Then, you should perform a great configuration files merging campaign to ensure having the up to date functionalities while keeping your own specific configuration (globally the XXX.conf and XXX.conf.rpmnew files).
It was not the case when I've tried it as soon as Fedora 7 was available, but I've successfully performed such an upgrade without difficulties some days ago.
The principle is globally the same when upgrading from Fedora core N to Fedora core N+1 (see this post), or from Fedora 7 to Fedora 8 (see this post).
In addition, the recommendations of Fedora project have greatly evolved and seem now complete.
This is some additional instructions in case you have specific issues (like I had):
Update your /etc/fstab file:
It is very important to use label (LABEL=myLabel) to identity your device instead of path (/dev/xxx). The identification has changed from Fedora core 6 to Fedora 7, generally from /dev/hdX to /dev/sdY BUT there is absolutely no certainties that X and Y will equal between versions.
Using labels ensure your mount points are always the same.
Particularly it ensures your root partition (/) will be the good, and your computer will well boot after upgrade.
To update the label of a device, you can use the tune2fs command.
Upgrade from Fedora core 6 to Fedora 7:
- do not forget to clean all the yum metadata with yum clean all,
- upgrade the Fedora release:
rpm -Uhv ftp://download.fedora.redhat.com/pub/fedora/linux/releases/7/Fedora/i386/os/Fedora/fedora-release*.noarch.rpm
- upgrade your repository, for instance for livna:
rpm -Uvh http://rpm.livna.org/livna-release-7.rpm
- remove and reinstall authconfig to avoid specific issue.
Upgrade from Fedora 7 to Fedora 8:
- do not forget to clean all the yum metadata with yum clean all,
- upgrade the Fedora release:
rpm -Uvh http://mirror.anl.gov/pub/fedora/linux/releases/8/Everything/i386/os/Packages/fedora-release-*.noarch.rpm
- upgrade your repository, for instance for livna:
rpm -Uvh http://rpm.livna.org/livna-release-8.rpm
Ensure there is no dependencies problem like explained into this post.
Then, you should perform a great configuration files merging campaign to ensure having the up to date functionalities while keeping your own specific configuration (globally the XXX.conf and XXX.conf.rpmnew files).
No comments:
Post a Comment
Thank you for your visit, let's share your point of view: