RRB <removethis.basv@removethis.gmx.at> wrote:
> Michael Heiming wrote:
> ...
> >>I wanted to install some new software that requires (among other
> >>libraries) 'libc.so.6(GLIBC_2.3)' (and i have glibc-2.2.5-38) so i
> >>downloaded and rpm'd glibc-2.3.2-6.i586.rpm.
> >
> > Congrats, you have effectively made your system unusable by
> > updating the most critical lib with a version which isn't suited
> > for your distro.

> oops! Effectively i was somewhat in doubt before i pressed enter after
> typing the command as root...

You should be sure what you are doing if you are running as root
if using 'rpm --nodeps/--force ...'
[..]
> ...
> > Boot from rescue image, mount your partitions somewhere and
> > relocate glibc*.rpm use "rpm --relocate .." to reinstall the rpm
> > package (man rpm). After that you might need to rebuild the rpm
> > db "--rebuilddb' or '--initdb'.

> So, with rpm --relocate glibc-2.3.2-6.i586.rpm (that's the new one) i
> should fix?
> Or should i make rpm --relocate with the older one?

You should try relocating/installing the older one of course,
since the newer doesn't work.

> In this case the problem of execution of newer software remains, and
> more, there's really no way, without reinstalling, to update libraries?

Albeit not impossible to run with multiple glibc versions, it
does require some work, so updating the whole system should be
easier, if you are not sure what you are doing.

--
Michael Heiming

Remove +SIGNS and www. if you expect an answer, sorry for
inconvenience, but I get tons of SPAM