From owner-freebsd-current Wed Jul 5 11: 0:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id B66C337BCC2 for ; Wed, 5 Jul 2000 11:00:30 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id LAA03814 for ; Wed, 5 Jul 2000 11:00:29 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id LAA38193; Wed, 5 Jul 2000 11:00:29 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Wed, 5 Jul 2000 11:00:29 -0700 (PDT) Message-Id: <200007051800.LAA38193@vashon.polstra.com> To: current@freebsd.org Reply-To: current@freebsd.org Subject: Re: /sys hierarchy In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Robert Watson wrote: > On Wed, 5 Jul 2000, John Baldwin wrote: > > > The headers will always be installed in the right place in > > /usr/include: Makefile's are editable. As far as kernel > > compiles, symlinks can be created in the work directory as > > one possible solution. For example, > > sys/compile/i386/GENERIC/netinet -> ../../../../net/inet. > > This would most likely result in netinet _not_ being split > > up. > > As much as I'd love a complete cleanup of sys/, this cure seems to be > worse than the problem. :-) Take this as another vote to leave net/ as > is, if only to keep the includes in kernel code in sync with includes in > userland code :-). I agree with Robert. Leave the network stuff where it is. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message