Yo!

What is segmentation fault?

I tried to install glibc latest update for my Linux redhat 9.0 but when I installed I noticed that it was my worst move I ever have done with any computer.

After the installation the Linux was totally destroyed. It was like somebody has dropped an E- bomb. Absolutely nothing was possible to do after that. I tried to uninstall the glibc but I allways got an answer: " segmentation fault"

After that all commands gave me same answer : " segmentation fault" " segmentation fault" " segmentation fault".



I tried to reboot computer but linux could not boot : reinstallation.

It gave me some some warnings while installing the glibc but I don't remember it.

Please advice.

What installation method are you using? (CD, network, FTP, etc.) Did you download it or buy it? If you bought it, have you contacted RedHat's technical support? If you downloaded it, did you verify the MD5 sum before burning to a CD?

Segmentation faults almost never occur in production code (which glibc certainly is), so my only thought is that somehow your installation medium got corrupted. glibc is an important part of many Linux programs, so corruption of it is very bad

this will answer what segmentation faults are: http://cs-www.bu.edu/help/unix/segmentation_fault.html

I downloaded it from www.redhat.com

I always check MD5 before burning or installing. MD5 errors are rare, luckily. Its a miracle that ftp is so good system as it is. But sometimes the files are corrupted. I download the files from the same country where I live and the speed is light speed, approx 500 kt/s.

I also compiled this glibc upgrade from source with command:

rpmbuild --rebuild --target=i686 glibc*

I have also tested ready made rpm's i386.rpm files and also these compiled files - they both fail similarly. Compiling went smoothly without any errors - or maybe I didn't notice any alarms...its always possible. It takes a long time.

I think this MD5 is checked twice...first by me and then by gcc.

I install like this:

rpm -Uiv glibc* but first with --test option. No dependency problems said to be by rpm. test goes smoothly, no problems found.

But when I actually install them, always the same result - OS is destroyed.

-Tommi

BTW...thanks for quick help!!!!

What happens if you just install the RPM without rebuilding? glibc should come by default with the RedHat installation (I would think). Maybe there is some problem with compilation that slipped by... it might be safer to use the already-compiled version.

FYI, there is a problem with one of the RPM's that RedHat released for glibc. If you happened to download that RPM, it could have hosed your PC.

First off, I believe that they fixed it. I friend of mine installed RH9 just fine, went to upgrade from the RHN up2date and it blew up. I tried it yesterday and it worked fine.

Heres the problem. The new RPM did not correctly upgrade glibc and ended up leaving the old glibc on you PC. Now every program that depends on it ends up seg faulting.

Here's the fix:
1) Reboot to a linux rescue prompt (use the CD and boot it).
2) Use RPM to uninstall the glib packages and install the new one.

Once that was done, everything worked again.

Jeff

Wow Hard to believe they missed that before it went out the door.

Is there anything in Linux that *doesn't* depend on glibc?

The kernel!
Everything in userspace does..in one way or the other. Even the java compiler and runtime use the functions complied into the standard C library.

Well...as I said I tried both updates:

1. readymade rpm's from redhats i386 folder

2. sources which I compiled later.

Same result with both tries. Os was totally destroyed.



-Tommi

Could you explain the bit about the linux rescue?
I mean, which rpm commands exactly? One has to
tell rpm to work with the packages on the original installed
linux, not with the packages on the rescue disk, right?

Actually I just experienced the same problem with the very latest
rpm packages, so redhat hasn't fixed anything yet:
http://www.linuxquestions.org/questi...pm+upgrade+RH9

ps, and take a look at bugzilla:

https://bugzilla.redhat.com/bugzilla...g.cgi?id=88456