> > Note, though, that it is **very** important that /usr/include/linux and
> > /usr/include/asm correspond to the default kernel that you are booting.
Fortunately, no. Otherwise one would have to recompile all programs
before booting a new kernel.
Alan wrote:
> I'm not convinced /usr/include/linux is sufficient. Perhaps we need
> a more explicit naming ?
You are too brief - sufficient for what?
I have contemplated the following change:
Everywhere in the kernel, replace
#include <linux/foo.h>
by
#include <kernel/foo.h>
and rename linux/include/linux to linux/include/kernel.
Now create a new directory linux/include/linux, look for the
public interfaces that the outside world should see, and
create files <linux/bar.h> containing these public interfaces,
probably included by <kernel/foo.h>.
Of course this is mainly psychology, but it might help:
Changes to <linux/bar.h> (perhaps other than additions)
are serious things, while changes to <kernel/foo.h> are
routine kernel development.
Andries
__
4:04pm up 1000 days, 4:54, 1 user, load average: 1.00, 1.00, 1.00
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/