Re: Continuing Annoyances...
On Thu, Jan 06, 2000 at 08:06:08AM -0500, Buddha Buck wrote:
> His rational is that /usr/include/linux headers are intended for
> userspace, so glibc had better know what they are. Userspace programs
> don't interact with the kernel directly, but go through glibc. The
> kernel headers are for kernel development, and shouldn't be used by
> userspace programs.
> If some software package truely needs to interface with the kernel w/o
> going though glibc (like a kernel module, for example), it should be
> written to find the kernel headers in /usr/src/linux/include/linux or
> wherever the user tells them they are (/linux/linux/include/linux on my
An unfortunate side-effect of this schism is that people writing modules
are often on Red Hat systems and just #include <linux/modversions.h> and
This drives me insane correcting this all the time. If somebody could get
them to quit it we would have distribution specific driver tarballs
floating around. :-/ It seems to prove my theory that _most_ kernel
hackers use a Red Hat derived disty.
Does the LSB draft specify a Linus-recommended solution?
This is Linux Country. On a quiet night, you can hear Windows reboot.