From owner-freebsd-arch@FreeBSD.ORG Mon Mar 2 02:54:48 2009 Return-Path: Delivered-To: arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 550A5106566B; Mon, 2 Mar 2009 02:54:48 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (agora.rdrop.com [199.26.172.34]) by mx1.freebsd.org (Postfix) with ESMTP id 2281C8FC0C; Mon, 2 Mar 2009 02:54:48 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id n222QQMD091705 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 1 Mar 2009 18:26:26 -0800 (PST) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id n222QQrK091700; Sun, 1 Mar 2009 18:26:26 -0800 (PST) Received: from fbsd61 by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA15727; Sun, 1 Mar 09 18:22:22 PST Date: Sun, 01 Mar 2009 18:22:02 -0800 From: perryh@pluto.rain.com To: rpaulo@gmail.com, julian@elischer.org Message-Id: <49ab42ca.YZ1mfcCDO0pvdDhv%perryh@pluto.rain.com> References: <20090301153010.GA58942@onelab2.iet.unipi.it> <49AAFD92.105@elischer.org> <8EBEEE24-6473-411D-AE3F-C4D1D3897E51@gmail.com> In-Reply-To: <8EBEEE24-6473-411D-AE3F-C4D1D3897E51@gmail.com> User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: arch@freebsd.org, net@freebsd.org Subject: Re: spliting kernel ipfw source ? (also involves sctp) X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Mar 2009 02:54:48 -0000 Rui Paulo wrote: > On 1 Mar 2009, at 21:26, Julian Elischer wrote: > > Luigi Rizzo wrote: > >> Hi, > >> I am planning to split netinet/ip_fw2.c in a number of smaller > >> files to make it more manageable, and while i do this I would > >> also like to move the files related to ipfw2 (namely ip_fw*c) > >> to a better place. > >> Any objection to moving them to sys/netinet/ipfw2 ? > >> Also, I can't help noticing that sys/netinet/ contains 36 > >> files related to sctp -- wouldn't it be the case to move > >> them (perhaps with the exception of the userland headers) > >> to a separate subdirectory ? > > > > for that matter it would be nice to put ALL teh protocols in > > their own subdirectories. > > Yes, that would be the perfect scenario, but I don't think that's > doable. > > SCTP can be moved because it hasn't matured enough to cause a > "moving nightmare". Perhaps everything can be moved, if hardlinks or symlinks are left in sys/netinet for those parts (mostly .h files, presumably) which have too much legacy to be moved outright.