Also, some of the media players didn't work properly, mainly because the system libraries updated to new versions and the media player executables were looking for a shared library that was no longer there.But this issue was not specific to the 64-bit cross-grade and would have been there if I updated to 32-bit Fedora 8./bin/bash mkdir -p /yum-repo-mirrors/f8everything cd /yum-repo-mirrors/f8everything wget -Y off -m "ftp://mirror.../pub/fedora/linux/releases/8/Everything/x86_64/os/Packages/" cd /yum-repo-mirrors/f8everything nice createrepo `pwd` /etc/yum.repos.d]# cat f8[f8everything] name=Fedora $releasever - $basearch baseurl=file:///yum-repo-mirrors/f8everything/ enabled=1 gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora Once I downloaded all the packages and made a solid system backup in preparation, I booted the Fedora 7 i386 machine from the Fedora 8 x86_64 DVD.If you're running database servers, dump them to a text SQL file to back them up before the update.Use the following script to grab the Everything directory and set up a local yum repository for it.You need to change the URL for wget to your fastest Fedora mirror.That way, if the cross-grade doesn't go well, you can quickly revert to the way the system was before you attempted the migration.
Everything still seemed to work in the virtual machine after the cross-grade.This happened to me with a Fedora Linux installation, and I finally decided to migrate.Over the years, I've talked to Fedora enthusiasts and Red Hat employees at Linux conferences about doing a cross-grade to 64-bit. However, I like to reserve this approach for when a critical number of system disks fail at once and I have absolutely no other option.Applications using boost::serialization in binary format suffered from the update, so I had to fix them manually.
At this point, my system had an odd mix of i386 and x86_64 RPMs on it.
Creating files for the new local repositories allows you to use them in preference to the default and files.