Re: spliting kernel ipfw source ? (also involves sctp)
- From: Rui Paulo <rpaulo@xxxxxxxxx>
- Date: Mon, 2 Mar 2009 00:18:30 +0000
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.
--
Rui Paulo
Attachment:
PGP.sig
Description: This is a digitally signed message part
- Follow-Ups:
- Re: spliting kernel ipfw source ? (also involves sctp)
- From: Robert Watson
- Re: spliting kernel ipfw source ? (also involves sctp)
- From: perryh
- Re: spliting kernel ipfw source ? (also involves sctp)
- References:
- spliting kernel ipfw source ? (also involves sctp)
- From: Luigi Rizzo
- Re: spliting kernel ipfw source ? (also involves sctp)
- From: Julian Elischer
- spliting kernel ipfw source ? (also involves sctp)
- Prev by Date: Re: spliting kernel ipfw source ? (also involves sctp)
- Next by Date: Re: spliting kernel ipfw source ? (also involves sctp)
- Previous by thread: Re: spliting kernel ipfw source ? (also involves sctp)
- Next by thread: Re: spliting kernel ipfw source ? (also involves sctp)
- Index(es):
Relevant Pages
|