On Tue, Jan 16, 2001 at 09:31:02PM +0200, Pekka Savola wrote:
> On Tue, 16 Jan 2001, Denis Ducamp wrote:
> > damn ! libc5 libraries are a different think from linux kernel 2.0 : that is
> > the magic of Linux systems ;-)
> >
> > Yes, linux 2.0 is old but libc5 isn't old and it's always used with linux
> > 2.2 kernels.
>
> Not so.
>
> Red Hat Linux 5.0 was AFAIK first to ship libc6. This was in Nov 97.
> The kernel was 2.0.32.
>
> 2.0 kernel was still being actively shipped in Debian 2.1, Red Hat Linux
> 5.2, and the like. The latest versions could be considered quite stable
> so it's still in use in many places.
>
> 2.0 kernel is _much_ more common than libc5.
Slackware had the contrary evolution : keeping the good and stable library
which is libc5 and upgrade to kernel 2.2.x . Slackware 4.0 is libc5 and
2.2.6 kernel based and dated 99/05/19.
No Slackware system have been available with a glibc 2.0 library : too big
and too unstable.
First Slackware glibc2 based is 7.0 dated 99/10/25 and glibc2.1.2 + 2.2.13
kernel.
I don't know any RedHat 5.x always running, they have all been upgraded to
6.[12] versions; nor any Debian running a 2.0.3x kernel . In fact the only
system I know with a 2.0.3x kernel is a slackware96 that I use to keep my
sources portable.
> > But why shouldn't I update softwares on systems that are less than 2 years
> > old ?
>
> Because most of these have already been updated and no one doing active
> development has access / caring for these?
I'm OK to test any version on my libc5 systems. Just send me the URL of a
snap and I'll give a try.
> > Hope libc5 will be supported back, I don't mind about linux kernel 2.0 .
>
> I'm pretty confident in saying that "patches will be accepted".
I hope libc5 support will be reintegrated soon, I know several people using
old computers to monitor networks installed with a few years system such as
slackware 4 which is only 20 months old.
All that I want is a libpcap with the "any" keyword as interface name and a
tcpdump without buffer overflow.
Denis Ducamp.
-
This is the TCPDUMP workers list. It is archived at
http://www.tcpdump.org/lists/workers/index.html
To unsubscribe use mailto:[EMAIL PROTECTED]?body=unsubscribe
