From: Ronan Cunniffe (ronan at domain cunniffe.net)
Date: Mon 15 Jul 2002 - 20:37:07 IST
Quoting "Wynne, Conor" <conor_wynne at domain maxtor.com>:
> OK I've read it, but I don't fully understand it ;-)
>
> But who the hell is gonna argue with linus, so I'll be a good little
> militant and follow my comrade in chiefs orders ;-)
> Got any more on the subject please?
Don't know if this is the "more" you're looking for....
Short version:
Libc et al are built to talk to kernel using interface spec X.
You build & install latest kernel, with its headers (spec Y).
Reboot to that kernel, and the first app to run into an X vs. Y difference
will barf when a library calls the kernel.
Solution: (other than waiting for a distro upgrade :-)
Build the latest and greatest kernel *with old headers*. If you need
something in the new headers, then you also need to rebuild libc et al. Linus
is advocating the separation of headers and code - headers go in /usr/include
and are matched to /usr/lib. Code (including the kernel) refers to that.
Ronan
This archive was generated by hypermail 2.1.6 : Thu 06 Feb 2003 - 13:17:53 GMT