spliting kernel ipfw source ? (also involves sctp)

perryh at pluto.rain.com perryh at pluto.rain.com
Sun Mar 1 18:54:48 PST 2009

Rui Paulo <rpaulo at gmail.com> 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.

More information about the freebsd-net mailing list