Well, you didn't have to reinstall; you could have simply installed a new glibc with the procedure I outlined earlier (rpm --root from the rescue environment; or a similar method for other distributions).
The only reasons I know of to reinstall a Linux system are:
* hard disk failure (duh!)
* root-kit installation
[If you have a good intrustion detection system, like tripwire, and you
really know what you're doing, it's POSSIBLE to clean a rootkit without
reinstalling. But you'll never be sure if you've cleaned it completely
or not.]
--Jeremy
On Thu, 2003-08-28 at 14:04, Jeffery Painter wrote:
> Speaking of glibc problems, I had installed Win4Lin and it's custom kernel
> croaked when running up2date causing massive glibc problems and forcing me
> to do a reinstall... just a word of warning to other win4lin users, be
> careful when updating glibc, it did not give me any dependency warnings
>
> - painter
>
>
> On Thu, 28 Aug 2003, Brian Weaver wrote:
>
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > I'm in the camp with Jeremy and the others who think it might be a
> > problem with glibc. I built a RH9 box from CDROM and then went to apply
> > the redhat updates that I rsync'ed from a mirror server.
> >
> > The glibc update from redhat encountered an error during the RPM update.
> > After that I only got segmentation faults until I booted with the RH9
> > cdrom and entered rescue mode to reapplied the updated glibc rpm. After
> > that the system booted OK and has been fine ever since.
> >
> > I've had the redhat glibc update fail on TWO totally different systems
> > to date. That's why I'm placing my vote in the updated glibc department.
> >
> > - -Weave
> >
> >
--
/---------------------------------------------------------------------\
| Jeremy Portzer [EMAIL PROTECTED] trilug.org/~jeremy |
| GPG Fingerprint: 712D 77C7 AB2D 2130 989F E135 6F9F F7BC CC1A 7B92 |
\---------------------------------------------------------------------/
signature.asc
Description: This is a digitally signed message part
-- TriLUG mailing list : http://www.trilug.org/mailman/listinfo/trilug TriLUG Organizational FAQ : http://trilug.org/faq/ TriLUG Member Services FAQ : http://members.trilug.org/services_faq/ TriLUG PGP Keyring : http://trilug.org/~chrish/trilug.asc
