> On Wed, Oct 06, 1999 at 05:20:07PM +0200, Bernhard Rosenkraenzer wrote:
> > On Wed, 6 Oct 1999, Benno Senoner wrote:
> >
> > > > Get the kernel RPM from 6.1.
> > >
> > > are you sure that there are no strange GLIBC conflicts ?
> >
> > Quite - AFAIR 6.0 uses glibc 2.1.1, 6.1 uses glibc 2.1.2, there's no big
> > difference between those. Besides, the kernel itself doesn't use glibc;
> > actually the kernel RPM doesn't contain anything that is linked against
> > any libc (unless you're installing kernel-pcmcia-cs).
> >
> > LLaP
> > bero
> >
>
> Although what you say is true, you're really looking at it from the wrong sid
> e.
> No, the kernel does not use glibc, however, glibc does use the kernel! Think
> about it. Part of the purpose of a C library is to translate a programmer's
> API to software interrupts to the kernel to complete some fucntionality like
> reading or writing a file.
>
> OK, that said, they've done a good job producing clean, separated code, and i
> t
> is likely that things will work OK, however, it would really take one of the
> developers to truely answer that question with 100% certainty. For example,
> we went from ipfwadm to ipchains in the kernel (although people name those by
> the command line utilities). Really, all that should have changed there is t
> hat
> a socket ioctl now accepts some different function value codes defined in
> a kernel level header.
Read /usr/src/linux/Documentation/Changes for the full story; however, I
think you'll find there's no problem with any 2.2 kernel to now on RHL 6.0.
--
Cheers
John Summerfield
http://os2.ami.com.au/os2/ for OS/2 support.
Configuration, networking, combined IBM ftpsites index.
--
To unsubscribe:
mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
