I'm not sure sure if using the "rm -fr" command did everything you were hoping, all these updates from Fedora are .rpms which are not individual files but more like a package of many files & scripts that once installed can be spread all over the filesystem, by using the "rm -fr" command you may only be removing a small part of the package as a whole. The beauty of the RPM package management system, is that RPM keeps track of everything that is part of a particular package, as well as making sure all dependencies are taken care of to keep your system running smooth (generally) and when using the right commands, you won't make a mess of your system.
For instance: My Mandrake is Red Hat based also, but when it comes to updating the kernel, they only give you a kernel-source package which is properly installed when using the rpm install command and because it is for building a new kernel or building dynamic kernel modules, it will make sure that gcc, make, and other necessary tools required for compiling kernel or modules are also installed as well as making sure to have the right versions of these tools. But you have to go through a complicated process (for a newbie) after to update your kernel with this source package before you can use it to compile modules as the modules version has to match the current running kernel, kernels updated via this route can/and usually will render your OS un-bootable with the new kernel if you make a mistake.
Fedora gives you a kernel update in the form of an .rpm, so all you do is issue one update command and you will succeed with little or no effort in compiling a new kernel because RPM does all the work for you due to scripts contained in the package which automate everything.
Generally there are three forms of commands to use with .rpm packages that will keep your system running smooth, because you will want to do one of three things when dealing with an .rpm ==> INSTALL, UPGRADE, REMOVE.
If I wanted to update/upgrade my kernel to the final current kernel update that I downloaded to my /root directory I issue this command:
[root@localhost ~]#rpm -Uvh kernel-2.6.18-1.2869.fc6.x86_64.rpm (for 64 bit)and everything will be done.
If I wanted to install Bittorrent GUI which is not already installed on my system, downloaded to my /root directory in two .rpm packages I issue this command:
[root@localhost ~]#rpm -ivh bittorrent-4.4.0-2.fc6.noarch.rpm bittorrent-gui-4.4.0-2.fc6.noarch.rpm (there is a space between the two packages listed in that command)(if you were to try and just install the Bittorrent GUI, RPM would tell you it can't because it needs the non-gui bittorent also as a dependency, if you are on-line it will tell you the other package is required, ask you if it is OK to install both, and download/install the dependency if you agree).
If I wanted to remove an .rpm package already install called pcsc-lite-libs... I would issue this command:
[root@localhost ~]#rpm -e pcsc-lite-libs-1.3.1-7.x86_64.rpm (even if both the i586 & x86_64 are installed, RPM will remove both if I just ask it to remove one as it takes care of dependencies when removing also, not leaving anything behind like Windows would do)
The (-Uvh) option represents "upgrade,verbose (let me see what's happening) and print 50 hash marks for the (h)
The (-ivh) is for installing and I want to see what's happening and it will be obvious with the 50 hash marks.
The (-e) stands for erase the package and take care of all dependencies (which could involve removing a more current dependency and replacing it (re-install) the former package required.) You cannot use the -vh option when removing.
The "rm -fr" command is for removing individual files and directories, .rpms are not individual files and are not unpacked/installed as a directory, .rpms are mostly just scripts used by gcc, make and a few other tools to build all necessary files required which are/can be spread through the entire filesystem & you would have your work cut out for you if you want to cleanly un-install an .rpm and take care of all dependencies which is all taken care of with one simple proper RPM command.
Why is your X-server not starting?? could it be because......
OR: If you have an NVIDIA graphics card like mine, you should install the kmod-nvidia .rpm package from www.rpm.livna.org
or Fedora extras (make sure to get the right one for your card), I have not installed it yet because I tried it in an earlier installation and could only get 800 x 600 resolution, I have a Intel 915 chipset to which there is a .rpm package available through Fedora extras or livna that takes care of that. For now I just hit "Ctrl-Alt delete" to re-boot when the X-server does'nt start, sometimes I have to do it three or four times in a row, does'nt bother me much right now and I will try both the 915 package and NVIDIA kmod later when I catch up.