Re: include conventions /usr/include/linux/sys ?

2000-11-22 Thread Mitchell Blank Jr
H. Peter Anvin wrote: > I suggested include/kernel and include/arch with include/linux and > include/asm being reserved for the kernel interfaces (ioctl and their > structures mostly.) That sounds good. One other refinement I would like to see is that architecture specific but always present

Re: include conventions /usr/include/linux/sys ?

2000-11-22 Thread Andi Kleen
On Wed, Nov 22, 2000 at 02:35:43PM -0800, H. Peter Anvin wrote: > Followup to: <[EMAIL PROTECTED]> > By author:"LA Walsh" <[EMAIL PROTECTED]> > In newsgroup: linux.dev.kernel > > > > Linus has mentioned a desire to move kernel internal interfaces into > > a separate kernel include directory.

Re: include conventions /usr/include/linux/sys ?

2000-11-22 Thread H. Peter Anvin
Followup to: <[EMAIL PROTECTED]> By author:"LA Walsh" <[EMAIL PROTECTED]> In newsgroup: linux.dev.kernel > > Linus has mentioned a desire to move kernel internal interfaces into > a separate kernel include directory. In creating some code, I'm wondering > what the name of this should/will

Re: include conventions /usr/include/linux/sys ?

2000-11-22 Thread Arjan van de Ven
In article <[EMAIL PROTECTED]> you wrote: > Linus has mentioned a desire to move kernel internal interfaces into > a separate kernel include directory. In creating some code, I'm wondering > what the name of this should/will be. Does it follow that convention > would point toward a linux/sys

include conventions /usr/include/linux/sys ?

2000-11-22 Thread LA Walsh
Linus has mentioned a desire to move kernel internal interfaces into a separate kernel include directory. In creating some code, I'm wondering what the name of this should/will be. Does it follow that convention would point toward a linux/sys directory? -l -- L A Walsh|

include conventions /usr/include/linux/sys ?

2000-11-22 Thread LA Walsh
Linus has mentioned a desire to move kernel internal interfaces into a separate kernel include directory. In creating some code, I'm wondering what the name of this should/will be. Does it follow that convention would point toward a linux/sys directory? -l -- L A Walsh|

Re: include conventions /usr/include/linux/sys ?

2000-11-22 Thread Arjan van de Ven
In article [EMAIL PROTECTED] you wrote: Linus has mentioned a desire to move kernel internal interfaces into a separate kernel include directory. In creating some code, I'm wondering what the name of this should/will be. Does it follow that convention would point toward a linux/sys

Re: include conventions /usr/include/linux/sys ?

2000-11-22 Thread H. Peter Anvin
Followup to: [EMAIL PROTECTED] By author:"LA Walsh" [EMAIL PROTECTED] In newsgroup: linux.dev.kernel Linus has mentioned a desire to move kernel internal interfaces into a separate kernel include directory. In creating some code, I'm wondering what the name of this should/will be. Does

Re: include conventions /usr/include/linux/sys ?

2000-11-22 Thread Andi Kleen
On Wed, Nov 22, 2000 at 02:35:43PM -0800, H. Peter Anvin wrote: Followup to: [EMAIL PROTECTED] By author:"LA Walsh" [EMAIL PROTECTED] In newsgroup: linux.dev.kernel Linus has mentioned a desire to move kernel internal interfaces into a separate kernel include directory. In creating

Re: include conventions /usr/include/linux/sys ?

2000-11-22 Thread Mitchell Blank Jr
H. Peter Anvin wrote: I suggested include/kernel and include/arch with include/linux and include/asm being reserved for the kernel interfaces (ioctl and their structures mostly.) That sounds good. One other refinement I would like to see is that architecture specific but always present