[NBLUG/talk] RPM Segmentation Fault

Todd Cary todd at aristesoftware.com
Sat Dec 6 21:43:01 PST 2003


Mark -

This is an OLD box (has a 1 GB secondary drive) - so old, I cannot 
remember what is in it other than most likely an early Pentium III - it 
was bound for the graveyard.

Do you know if the up2date saves off it's list of tagged headers?

Let me see if the BIOS displays the CPU on boot.

Which commands should not have worked if it was a version problem with 
glibc?

Todd

Mark Street wrote:

>AHA!!!!
>
>glibc....  Is this a 686 processor?  I will tell you what.  After your UPdate 
>finishes see if you can run any of the commands....  I bet you can't.
>
>Here is what is happening, the i386 version of the glibc package is being 
>installed which breaks the system badly... bad enough so that you cannot use 
>RPM to fix what you have broken.
>
>Several of my students this semester did this in class.  We had to rescue 
>their system....
>
>http://www.streetchiro.com/linux/HelpMeFixIt
>
>YOU MUST make sure that you install the glibc i686 package of glibc!  If you 
>have to download it manually and install it by hand then run UP2date.  Maybe 
>it is a bug in up2date?
>
>
>On Saturday 06 December 2003 21:09, Todd Cary wrote:
>  
>
>>I ran up2date to the point where it was going to start the update.
>>There was a long list of packages that were flagged for update and I am
>>not sure if the flagged list went into a file.  However, amoung those
>>that appeared was glibc.  Some of the messages on Google for
>>segmentation erros had glibc in the text.  Not much help, particularly
>>with the long list of packages.
>>    
>>
>
>
>  
>

-- 




More information about the talk mailing list