X-pop3-spooler: POP3MAIL 2.1.0 b 4 980420 -bs-
Date: Tue, 15 Sep 1998 14:53:11 -0500 (CDT)
From: Dustin Marquess <jailbird AT alcatraz DOT fdf DOT net>
To: david <david AT kalifornia DOT com>
cc: pcg AT goof DOT com, beastium-list AT Desk DOT nl
Subject: Re: libc-5.4.22?!?
In-Reply-To: <199809150944.CAA03397@Midnight.Hacking.in.the.land.of.Kalifornia.com>
Message-ID: <Pine.LNX.4.02A.9809151451290.2888-100000@alcatraz.alcatraz.fdf.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: Marc Lehmann <pcg AT goof DOT com>
Status: RO
X-Status: A
Content-Length: 984
Lines: 25


	When I installed glibc a while ago it was fairly unstable and
unreliable.  I beleive it is better now, but I'm going to give it a little bit
more time before I switch (I'll proally switch when the 2.2.x kernels come out).
libc-5 has been out alot longer, therefore it has been more tested more...


On Tue, 15 Sep 1998, david wrote:

> Reply to mail from Shawn Leas about libc-5.4.22?!?
> -----------------
> > Agreed, RedHat is being irresponsible for having such an old libc5 rusting
> > there for compatibility reasons.
> 
> Aye, please read my previous :)
> 
> > libc5 maybe isn't "going away" anytime soon, but should.  And you're
> > right, of course, that it isn't a "slackware" thing, but since debian,
> > RedHat, Suse (I think) etc have gone libc6, it is becoming an increasingly
> > "Slackware" thing.
> 
> I like many other administrators will probably fully migrate as time
> permits and the need arises.  The axiom "if it ain't broke don't fix it"
> comes to mind :)