Upgrading Fedora
Appearance
Fedora 9 -> Fedora 10[edit | edit source]
- Check the Fedora 10 Installation Guide and Fedora 10 Release Notes
fedora-release
packages can be found atftp://download.fedora.redhat.com/pub/fedora/linux/releases/10/Fedora/i386/os/Packages/fedora-release-10-1.noarch.rpm
- GDM starts on tty1 by default, not tty7.
- anaconda by default now refers to encrypted devices by UUID, not by device name, to better handle device name changes. An encrypted device using partition
/dev/sda1
with UUID12345678-1234-1234-1234-123456789012
would now be called/dev/mapper/luks-12345678-1234-1234-1234-123456789012
instead of/dev/mapper/luks-sda1
. You may wish to make the same changes on your system on upgrade; if you do, make sure to runmkinitrd
afterwards. - If you use non-root encrypted devices, you will need to re-run
mkinitrd
for any older kernels that you want to still boot on the system. - It's been reported that there are problems with Pidgin i.e.:
pidgin-2.5.2-2.fc9.i386 from installed has depsolving problems - Error: Missing Dependency: libedataserver-1.2.so.9 is needed by package pidgin-2.5.2-2.fc9.i386 (installed)
- the fix was to remove Pidgin
Fedora 8 -> Fedora 9[edit | edit source]
- Check the Installer section in Release Notes)
- After "the incident" you should use updated fedora-release packages from
rpm -Uvh ftp://download.fedora.redhat.com/pub/fedora/linux/updates/9/i386.newkey/fedora-release-*.noarch.rpm
- If you are running as a
xen
Host (Dom0) you should not upgrade to Fedora 9. [1] - Upgrading the thunderbird package will fail . The current workaround is
yum remove thunderbird; yum install thunderbird>
. - If you are upgrading to Fedora 9 and use
emacs
, you must upgrade to the latest version ofemacs
for your prior release to ensure a clean upgrade. Fedora 8 users must haveemacs-22.1-10.fc8
or later, while Fedora 7 users must haveemacs-22.1-7.fc7
. Bug report here . - Due to the switch from sysvinit to Upstart , it is recommended that users who do an upgrade on a live filesystem to Fedora 9 reboot soon afterwards. If you do not reboot, you may want to take careful note of any '/etc/inittab.rpmsave' or '/etc/inittab.rpmnew' files. When rebooting after an upgrade then be aware that sysvinit that was used to start the system can't be used to shut it down.
- You may find that after upgrading, you can no longer log in to GNOME. If this is the case, use ctrl-alt-F1 to access command prompt, then check the tail of .xsession-errors. If you see a comment like "(named color or font does not exist)", then you may be able to fix this using http://matthew.peach.net.nz/2008/05/18/how-to-fix-badname-named-color-or-font-does-not-exist-error/.