Re: [RFC] Splitting kernel headers and deprecating __KERNEL__

Matthew Wilcox
2004-11-26T23:03:07Z

On Thu, Nov 25, 2004 at 04:20:06PM -0200, Alexandre Oliva wrote:
> This means these headers shouldn't reference each other as
> linux/user/something.h, but rather as linux/something.h, such that
> they still work when installed in /usr/include/linux. This may
> require headers include/linux/something.h to include
> linux/user/something.h, but that's already part of the proposal.

That's going to take severe brain-ache to get right ... and worse,
keep right. These headers aren't going to get tested outside the kernel
tree often. So we'll have missing includes and files that only work if
the <linux/> they're including is a kernel one rather than a user one.

I'm not particularly stuck on the <user/> namespace. We could invent
a better name. How about <kern/> and <arch/> to replace <linux/>
and <asm/>? Obviously keeping linux/ and asm/ symlinks for backwards
compatibility.

--
"Next the statesmen will invent cheap lies, putting the blame upon
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince
himself that the war is just, and will thank God for the better sleep
he enjoys after this process of grotesque self-deception." -- Mark Twain