[NBLUG/talk] RedHat 9 gives segmentation fault after glibc update

[Mark Street]

Once bit twice shy...been there done that...  See my post from May 21, 2003 
15:24 - RH Question
......
Generally there are only a few packages that are i686 specific, kernel, glibc, 
openssl, kernel-smp, etc.

As a general rule always pick the package closest to your architecture, then 
choose the more general arch.  Generally you can't go wrong with i386 
packages.

Most packages can be recompiled as i686 if desired but I think redhat has 
picked out the packages that make the most difference performance wise and 
distributed i686 specific packages.

NOTE: Things don't work very well if you install i686, then Freshen or UPgrade 
with i386 packages....  Keep it consistent, remember which packages are i686 
specific when it comes time to upgrade a package.....  I know....from finding 
out the hard way..
........

On Tuesday 03 June 2003 10:44, Frank Ball wrote:
> Yesterday I was upgrading a RedHat 9 machine and it tried to install the
> i386 glibc rpm over a i686 glibc rpm.  It totally trashed the machine.
> Pretty much every command segfaulted.  I was able to fix it today, but I
> thought I let people know about the potential problem, some tips to
> avoid it, and how to fix it.
>
> There is no depedency check for this.  Many people have been caught by
> it one way or another, and RedHat doesn't seem to give a rat's ass.
>
> I was using apt-get to do the upgrade, and I did not have the
> architecture specified in the /etc/apt/apt.conf file:
>
> APT {
>     Clean-Installed "false";
>     Get {
>         Assume-Yes "false";
>         Download-Only "false";
>         Show-Upgraded "true";
>         Fix-Broken "false";
>         Ignore-Missing "false";
>         Compile "false";
>         Architecture "i686";
>     };
> };
>
> This is the way it looks now, with the "Architecture "i686";" line
> added.  It now upgrades properly.
>
> I got the fix from this page:
>
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=88456
>
> Use CD#1 as a rescue image (type "linux rescue" at the boot prompt).
>
> (b) rpm --root=/mnt/sysimage -qa | grep glibc
>
> showed that glibc-common was updated, but both
> glibc packages exist in the rpm database.
>   OLD: glibc-2.3.2-11.9
>   NEW: glibc-2.3.2-27.9
>
> (2) removed glibc-2.3.2-11.9
>     rpm --root=/mnt/sysimage -e glibc-2.3.2-11.9
>
>     reinstalled glibc and glibc-common from the CDROM
>       they were under /mnt/source/RedHat/RPMS/
>
>     rpm --root=/mnt/sysimage -Uvh --force glibc-2.3.2-11.9.i686.rpm
> glibc-common-2.3.2-11.9.i386.rpm
>
> (3) test it out
>     chroot /mnt/sysimage
>
> You will know if the system fixed if the chroot does not segfault.

-- 
Mark Street, D.C.
Red Hat Certified Engineer
Cert# 807302251406074
--
Key fingerprint = 3949 39E4 6317 7C3C 023E  2B1F 6FB3 06E7 D109 56C0
GPG key http://www.streetchiro.com/pubkey.asc