Reporting on experiences upgrading an FC2 (+ some 3rd party packages) system on an IBM Thinkpad A21p notebook to FC3T1, but not without some glitches. This system has survived upgrades from RH7.x through RH8.0, RH9, FC1, FC2T3, and FC2 (not to mention W98_2ed, WinXP). Booted the installer kernel from grub and selected NFS upgrade (have a local copy of the FC3T1 tree exported). First, encountered a lockup when the installer attempted to access the network - should have anticipated this as this system has had to be booted with acpi=off for some time to avoid this type of lockup. Rebooted with acpi=off and got a bit farther. Filed bug #128711. Seems that many installation problems could be avoided if the installation kernel omitted ACPI. Any compelling reasons not to do that? Also would be friendly if the installer had the ability to detect known hardware configurations that have trouble with ACPI and automatically add it to the GRUB kernel line. Opinions? Next encountered an anaconda crash, bug #127713, due the existence of /selinux - again this could have been anticipated given a bugzilla search and/or remembering/reviewing what had already been discussed on this list. Clobbered /selinux and tried again. Hopefully this will get fixed before FC3T2. This system is dual-boot with WinXP on the single hard drive, and would appear to be vulnerable to the installer bug that renders windows unbootable (sfdisk and fdisk disagree on geometry) but encountered no problems with XP, presumably as the upgrade should not have touched the partition table. [Ought to dump XP anyway and free up the space - only remaining need given the state of OOo and Crossover Office is to use the built-in Winmodem that never has gotten Linux support. A PCMCIA modem could fix that.] This time the upgrade proceeded to completion. Next tried to run "yum upgrade" on rawhide repository and found conflicts with left-over ATrpms libraries: ... Running test transaction: Errors reported doing trial run file /usr/lib/libglib-2.0.so.0 from install of glib2-2.4.4-1 conflicts with file from package libglib2.0_0-2.4.1-0.99_4.rhfc2.at file /usr/lib/libgmodule-2.0.so.0 from install of glib2-2.4.4-1 conflicts with file from package libglib2.0_0-2.4.1-0.99_4.rhfc2.at file /usr/lib/libgobject-2.0.so.0 from install of glib2-2.4.4-1 conflicts with file from package libglib2.0_0-2.4.1-0.99_4.rhfc2.at file /usr/lib/libgthread-2.0.so.0 from install of glib2-2.4.4-1 conflicts with file from package libglib2.0_0-2.4.1-0.99_4.rhfc2.at file /usr/lib/librpm-4.3.so from install of rpm-4.3.2-0.6 conflicts with file from package librpm4.3-4.3.1-0.3_27.rhfc2.at file /usr/lib/librpmbuild-4.3.so from install of rpm-4.3.2-0.6 conflicts with file from package librpm4.3-4.3.1-0.3_27.rhfc2.at file /usr/lib/librpmdb-4.3.so from install of rpm-4.3.2-0.6 conflicts with file from package librpm4.3-4.3.1-0.3_27.rhfc2.at file /usr/lib/librpmio-4.3.so from install of rpm-4.3.2-0.6 conflicts with file from package librpm4.3-4.3.1-0.3_27.rhfc2.at Did "yum remove libglib2.0_0 librpm4.3" which fixed that problem, checked for any other old rpm cruft (rpm -qa --qf "%{INSTALLTIME} % {NAME} %{VERSION} %{RELEASE}\n" | sort -r >RPMS_by_Install_Time), and finding none, tried the update again. Updated 150 packages. Lots of errors similar to: /usr/share/gnome/help/wireless/fr/wireless.xml:38: parser error : Entity 'legal' not defined &legal; ^ /usr/share/gnome/help/wireless/fr/wireless.xml:45: parser error : Entity 'Eacute' not defined <firstname>&Eacute;quipe de documentation</firstname> ^ /usr/share/gnome/help/wireless/fr/wireless.xml:76: parser error : Entity 'ucirc' not defined <date>Ao&ucirc;t 2003</date> ^ The files are from gnome-applets. Have seen this sort of error before, but couldn't find this under gnome-applets on Bugzilla, so filed Bug #128717. Not too bad so far for a T1 upgrade. Rollin', rollin', rollin'... Phil