On Sat, 29 May 1999 11:53:47 +1000 
 matthew green <mrg@eterna.com.au> wrote:

 >    	- many user programs will need to be modified to include the
 >    	  correct headers
 > 
 > why?

...um, because there are userland programs that include these source
files...

 >    While we are at it, why don't we do the same for net?
 >    	net/{inet,ccitt,atalk,iso,natm,ns}
 >    
 >    Then we can break *all* userland programs that use the network.
 > 
 > i don't see why moving the kernel sources around has to do with
 > breaking what the userland sees?  that's why we install headers
 > individually from each directory now, isn't it?
 > 
 >    But that is easily repairable by ln -s net/inet netinet in /usr/include
 > 
 > this just seems gratuitious.  if we need /usr/include/netinet,
 > just use it and don't litter /usr/include with symlinks that
 > serve no purpose.

...so, your proposal is to have user includes and system includes in
a completely different heirarchy.

i.e. in userland, <netinet/in.h> but in the kernel <net/inet/in.h>.

"No thanks."

        -- Jason R. Thorpe <thorpej@nas.nasa.gov>