Hey gang; I didn't see a notice here, so I thought I would ask:
I am seeing glibc-2.3.2-10mdk up on (some of) the mirrors. Is this version o.k. to upgrade to from -8 ? Bob On Tuesday 29 July 2003 03:40 pm, parag shah wrote: > On Tue, Jul 29, 2003 at 12:53:11PM +0200, Jan Ciger wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > J.A. Magallon wrote: > > | HI, just a WARNING > > | > > | I was updating remotely a machine and when it got to update to > > | glibc-2.3.2-9mdk, some scriptlet failed and box is broken. > > | Even ls just gives core-dump. > > | > > | I am able to start a sash. Any way to recover remotely ? > > | And locally ? > > | > > | :(, Cooker risks :) > > | > > | TIA > > > > I didn't have any problems with the update. To recover, you will have to > > boot from a CD, get the older version of the glibc RPM and install it. > > > > Good luck :-) > > I had same fatal glibc update that coredumped my machine left and right. > I managed to recover by downloading glibc-2.3.2-5mdk from a cooker > mirror ( It is also on the Beta1 cd of 9.2). I then used mc to extract > files from the glibc rpm and copied them on to my defunct machine booted > into rescue mode. once i manged to boot in i then had to set rpm > database right by force installing the same glibc-2.3.2-5mdk and its > devel package. Now things are back to where it was befor that fatal > glibc update. > > Hope this helps to anyone who got burnt cause of glibc update today. > > regards, > > parag
