> > There are perfectly valid uses of kernel headers from userspace. For > > example if a program uses the netlink interface, it should include > > <linux/netlink.h>. It's the interface definition after all. > > > > Glibc headers also include <linux/*> and <asm/*> in quite few places. > > But these files in /usr/include/ aren't provided by the kernel anymore.
They are provided by _one_ kernel, not necessarily the running kernel. That doesn't make them any less a kernel header. So if some userspace program depends on header <linux/x.h> to get the interface definition for feature x, and you remove <linux/x.h> from the current kernel, it _will_ break the userspace program some time later, when glibc picks up the new kernel. Having said that that, <asm/segment.h> may or may not be validly exported to userspace. Miklos - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
