Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 2 Mar 2009 18:30:27 +0000 (GMT)
From:      Robert Watson <rwatson@FreeBSD.org>
To:        Rui Paulo <rpaulo@gmail.com>
Cc:        arch@freebsd.org, Julian Elischer <julian@elischer.org>, net@freebsd.org
Subject:   Re: spliting kernel ipfw source ? (also involves sctp)
Message-ID:  <alpine.BSF.2.00.0903021827400.11098@fledge.watson.org>
In-Reply-To: <8EBEEE24-6473-411D-AE3F-C4D1D3897E51@gmail.com>
References:  <20090301153010.GA58942@onelab2.iet.unipi.it> <49AAFD92.105@elischer.org> <8EBEEE24-6473-411D-AE3F-C4D1D3897E51@gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help

On Mon, 2 Mar 2009, 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".
>
> I vote for "ipfw" like Sam, BTW.

I think massively rearranging things doesn't by us much in terms of beauty, 
but does give us a lot in terms of hassle, given current assumptions of 
alignment between the layout of /usr/include and the layout of /usr/src/sys. 
We'd need to introduce new explicit mappings to install include files in their 
old locations (which are required by applications), etc.  For a change with 
such a minor benefit, the hassle will be huge.  I'm fine with renaming the 
ipfw .c files and leaving in netinet, but let's not get carried away.

Robert N M Watson
Computer Laboratory
University of Cambridge



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.0903021827400.11098>