> Ok, this isn't entirely a kernel issue, but here's the problem:
> if you include linux/types.h, glibc totally barfs...
Indeed - don't do that.
> Also, why are programs including linux/*? That should be reserved if they
> directly interface with the kernel, correct? modules, stuff like procps
> perhaps? Is it stupid programmers or was it simply because standard
> libc /includes used current linux source for types.h?
Under libc5 it was OK to do that, and so people saw no reason not to.
That's not the case with glibc.
p.