Hi all.
Proposal for directory structure in the kernel:
usr/include <= _all_ include files
usr/include/{net,sys,..}
usr/include/arch/$(ARCH) <= arch specific include files
*1
usr/klibc <= klibc files
usr/klibc/arch/$(ARCH) <= arch specific config and files
except include files
usr/kinit <= program integrated in the kernel
usr/kinit/nfsmount <= used by kinit, and stanalone
usr/kinit/ipconfig <= as do
*2
*1
Combine all header files in a single tree with an arch specific
place when relevant.
*2
Will we clutter this up over time or is this flat structure OK?
The reason to keep nfsmount/ipconfig under kinit is that kinit are
dependent on the two.
Sam
On Fri, 30 Jul 2004 22:03:42 +0200 Sam Ravnborg wrote:
| Hi all.
|
| Proposal for directory structure in the kernel:
|
| usr/include <= _all_ include files
| usr/include/{net,sys,..}
| usr/include/arch/$(ARCH) <= arch specific include files
| *1
Is this supposed to address linux-abi header files in the kernel
tree also?
| usr/klibc <= klibc files
| usr/klibc/arch/$(ARCH) <= arch specific config and files
| except include files
|
| usr/kinit <= program integrated in the kernel
| usr/kinit/nfsmount <= used by kinit, and stanalone
| usr/kinit/ipconfig <= as do
| *2
|
| *1
| Combine all header files in a single tree with an arch specific
| place when relevant.
|
| *2
| Will we clutter this up over time or is this flat structure OK?
| The reason to keep nfsmount/ipconfig under kinit is that kinit are
| dependent on the two.
--
~Randy
Sam Ravnborg wrote:> Hi all. > > Proposal for directory structure in the kernel: > > usr/include <= _all_ include files > usr/include/{net,sys,..} > usr/include/arch/$(ARCH) <= arch specific include files > *1 > > usr/klibc <= klibc files > usr/klibc/arch/$(ARCH) <= arch specific config and files > except include files > > usr/kinit <= program integrated in the kernel > usr/kinit/nfsmount <= used by kinit, and stanalone > usr/kinit/ipconfig <= as do > *2 > > *1 > Combine all header files in a single tree with an arch specific > place when relevant. >Looks like it's already well integrated to me?> *2 > Will we clutter this up over time or is this flat structure OK? > The reason to keep nfsmount/ipconfig under kinit is that kinit are > dependent on the two. >I think this is fine. -hpa
On Fri, Jul 30, 2004 at 10:55:36AM -0700, Randy.Dunlap wrote:> On Fri, 30 Jul 2004 22:03:42 +0200 Sam Ravnborg wrote: > > | Hi all. > | > | Proposal for directory structure in the kernel: > | > | usr/include <= _all_ include files > | usr/include/{net,sys,..} > | usr/include/arch/$(ARCH) <= arch specific include files > | *1 > > Is this supposed to address linux-abi header files in the kernel > tree also?No, this is purely header files for klibc. The linux-abi headers needs to have a separate home. Sam
Sam Ravnborg wrote:> > No, this is purely header files for klibc. > The linux-abi headers needs to have a separate home. >Absolutely. After all, part of the whole point with linux-abi is to separate out the stuff used by only one user (kernel, klibc, glibc, etc) as opposed to all of the above. -hpa