So, I brought up the idea of a linux/sys for kernel level include files.

A few other people came up with a desire of a 'kernel' dir under
include, parallel w/linux.

So I ran into a snag with that scenario.  Let's suppose we have
a module developer or a company developing a driver in their own
/home/nvidia/video/drivers/newcard directory.  Now they need to include
development files and are used to just doing the:
#include <linux/blahblah.h>

Which works because in a normal compile environment they have /usr/include
in their include path and /usr/include/linux points to the directory
under /usr/src/linux/include.

So if we create a separate /usr/src/linux/include/kernel dir, does that
imply that we'll have a 2nd link:

/usr/include/kernel ==> /usr/src/linux/include/kernel  ?

If the idea was to 'hide' kernel interfaces and make them not 'easy'
to include doesn't providing a 2nd link defeat that?

If we don't provide a 2nd link, how do module writers access kernel

If the kernel directory is under 'linux' (as in linux/sys), then the
link is already there and we can just say 'don't use sys in apps'.  If
we create 'kernel' under 'include', it seems we'll still end up having to
tell users "don't include files under directory "x"' (either kernel/ or

Note that putting kernel as a new directory parallel to linux requires
adding another symlink -- so is that solving anything or adding more
administrative "gotcha's"?


L A Walsh                        | Trust Technology, Core Linux, SGI
[EMAIL PROTECTED]                      | Voice/Vmail: (650) 933-5338

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at

Reply via email to