* Drew Northup <[EMAIL PROTECTED]> [010323 07:28]:
> As for the kernel being _part_of_ glibc, I think that you need to
> check your references again.
John was precise about this -- the kernel *headers* are part of glibc. I
have recently discovered this fact on my own in kernel module
programming. All I could recall was the symlink method of libc5. I had
heard the method had changed, but until I read the document
README.headers shipped in the Debian package kernel-package (I can email
to whoever wants it! :) I hadn't understood the new method.
The new method, in a nutshell, has glibc provide the kernel headers
against which it was compiled. This means userland applications will be
compiled with the same information as glibc was compiled with, and
everything will work as expected. However, kernel modules cannot be
compiled so blindly -- trying to load a kernel module programmed on a
Debian unstable system into a linux 2.2.18 kernel will fail miserably
because the module was compiled against 2.4.2-pre2 (at the moment) no
matter the running kernel version.
glibc provides its own version of kernel headers. (Which *does* sound
strange to me too, but many of our best and brightest have worked on the
problem and invented this as the solution.)
> John Summerfield wrote:
>
> > Kernel headers are part of glibc and commonly have symlinks into
> > /usr/src/linux
--
Earthlink: The #1 provider of unsolicited bulk email to the Internet.
