Re: My upgrade problems

["Jamieson M. Cobleigh" <jcobley cs rutgers edu>]

-----BEGIN PGP SIGNED MESSAGE-----

> > What seems to have happened during the upgrade was RPMS libc-5.0 got
> > upgraded before files like /bin/sh were upgraded.  This meant libc-5.0 was
> > "removed" and /bin/sh was still the old version, so it needed libc-5.0 not
> > libc-6.0.  At this point rpm was a very confused program - it thought I
> > had two version of libc-5.0 installed (the 4.2 version and the 5.0
> > version).  I tried several things to get one libc-5.0 installed, with
> > little success.  Doing some ldd's on files, I noticed some were linked to
> > libc-5.0 and some were linked to libc-6.0.  At this point I realized I
> > would have to spend a lot of time fixing everything, or I could just try a
> > full install. 
> When you did an upgrade did you use the upgrade program or try to run rpm
> -Uvh? The upgrade program has its own sh so it shouldnt have needed a
> newer one.

I used the upgrade program.  I guess my supposition must have been
incorrect.  Al I know is that when I the install completed, rpm thought
there were two versions of libc installed (the 4.2 and 5.0 one), and
running ldd on /bin/sh showed it still pointing to libc-5.0.

Jamie

-----BEGIN PGP SIGNATURE-----
Version: 2.6.2

iQCVAwUBNIyvT/OeQ9xp/aqNAQEo3gQAqwPMeypkHxZFcCUUsU0mHpB63JP3Cu57
jSVasyoYbl7Wq0pvKNbkehq0TayRPqhihsigQgnxyqQpNDnp1KwP4sqf78t0+Sk/
yvmnWXGPvmJOogLivX0FjHrgEHLwP38aIOV35K+v6nVuf98rnUY+MrMtFCp9qIm6
1HZ9wAODfao=
=Z3DA
-----END PGP SIGNATURE-----