[klibc] Re: klibc structure in the kernel

[H. Peter Anvin]

Sam Ravnborg wrote:
> 
> The linux kernel have traditionally combined files by usage more than
> by architecture.
> All architecture specific headerfiles are in include/asm-$(ARCH)

What's the difference between include/asm-$(ARCH) (vs include/) versus 
usr/include/arch/$(ARCH) vs usr/include?  The only difference is a slash 
rather than a dash, and I think the slash makes more sense.

> Many architecture specific drivers are in drivers/..
> 
> Having all header files in one place also makes it easier to grep them all,
> Think of this from a user perspective, where the other arch bits are
> of much less relevance than the headers.
> 
> A naive user would expect to find all include files in one place,
> and not hidden somewhere under a directory full of .c files.

Well, the sick part with the current Linux kernel tree is that it has 
BOTH...

I think include/asm-$(ARCH) is a hideously annoying idea; it's really 
frustrating while editing stuff in arch/$(ARCH).

That being said, I'm ok with usr/include/arch/$(ARCH) rather than 
usr/lib/arch/$(ARCH)/include.

	-hpa