> I would really like to see include/linux contain only the definitions
> that can be visible to user space. I don't like going into
> /usr/include/linux and seeing thousands of lines of hardware
> bit definitions.
>
> How about making some more directories for things that need to be
> shared among kernel source: include/fs, include/kernel, and so on?
Has anyone considered the X Window model, in which the public interfaces
for a widget "foo" are in path/Foo.h and private, internal goop is in
path/FooP.h ? Then if you see "#include <path/FooP.h> you know that
either (a) you are reading the code for the foo widget, or (b) the
author is engaged in sawing the limb on which he sits.
Or have I misunderstood the problem?
-- Mark H. Wood, Lead System Programmer mwood@IUPUI.Edu Legacy system: installed before the speaker arrived; therefore outdated, despised, to be replaced ASAP.