Re: HELP! I'v kicked my Linux (SuSE 8.1)
From: Remi Villatel (maxilys_at_SPAMCOP.tele2.fr)
Date: Sat, 27 Mar 2004 23:55:09 +0100
Jens-René Wiedemann wrote:
> I have a big problem:
> I wanted to update the GLIBC on a remote SuSE 8.1 System... I compiled
> glibc-2.3.2 with linuxthreads (configure+make) then I run make install...
> while doing this, i got an error:
It just reminds me yesterday when I partially broke my KDE because of a
badly compiled library...
Luckily I didn't broke the libc and I could re-install with RPM what was
erased by make install.
I hope you have the CDs of your SuSE 8.1. That's the only solution. Boot on
the first CD, leaving your hard disk out of the way, choose repair mode,
mount your HD, chroot and re-install the glibc package which is on some CD.
(I can't tell you which because I only have SuSE 7.2 and 8.2 but I guess it
will be on the first one.)
If you want to be absolutely sure that everything is back in order, you can
re-install the whole system. BUT either you must have a fresh backup of your
/home or it must be on another partition in order that an installation leave
in untouched. (Loosing one's /home is a real PITA!)
And next time, you want to update a vital part of your system, choose the
RPM way. If a package isn't in your version of SuSE, look in the next one.
My favorite source of SuSE RPMs:
You will have to resolve some dependencies and to apply some gentle --force
here and there but you will be sure (at least) that what you install is
And I know what I'm talking about because I installed parts of SuSE 9.0 over
my SuSE 8.2 in order to be able to install KDE 3.2.1 although the RPM
packages were supposed to be for version 8.2. Luckily, I have a 512k DSL
connection because I've realized that I looooove downloading! ;-)
Well, t'was just my 2 cents...