On Fri, 2008-06-13 at 13:34 -0400, Alheid, Gregory wrote: > Well that is the issue, how do I find out if they are needed.
Assuming you have no third party packages, you can just start removing them, it's unlikely you'll have any trouble. We ran into an issue where we had some software that we compiled from source back int he RHEL3 days that died once we removed the old openssl stuff and another that died after we removed the old imlib. We had to upgrade/recompile this software from newer versions to use the newer libraries included in RHEL5. If you don't have any of this at all your probably pretty clear. I guess the only way you'll know is to remove them and see what breaks, but looking at the package list you provided I'd guess you want have too many issues. > Using KSH as an example, just removing the pdksh RPM would > be is an issue since I'm a user of ksh. I did find the new > RHEL-5 KSH RPM, ksh-20060214-1.7.x86_64, so I was able to > removed the RHEL-4 RPM and installed the new RPM. If you see something that you know you use, you'll have to go look for a replacement/upgrade. The KSH package is an example. To be totally honest, I think they should have made ksh "obsolete" pdksh so that it was automatically upgraded rather than having to deal with it manually after the fact but instead it's listed as "conflict". > > Here's a link to a Redhat KB article that touches on it: > > > http://kbase.redhat.com/faq/FAQ_103_10686.shtm > > On reviewing the URL given, it indicates to run the yum list extra > command. This shows all the RHEL-4 RPMs plus the three IBM Tivoli RPMs. Right, the URL was given as an example to show that it's a normal issue. Notice the line "This will list the packages installed on the system that are not available in any yum repository listed in the config file, showing what is 'left over' from the previous version of Red Hat Enterprise Linux" The command actually shows any packages not available via a yum repository (like many third party packages). Unfortunately having some old, obsolete packages left over after an upgrade is just a normal side effect of the process which you, as an administrator, have to deal with. It's just like going through and looking at all of the .rpmsave/.rpmorig files that are left hanging around and merging any changes that you want into you old config files. Later, Tom _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
