Date: Fri, 6 Mar 2009 12:40:47 +0000 (UTC) From: Vadim Goncharov <vadim_nuclight@mail.ru> To: freebsd-arch@freebsd.org Subject: Re: spliting kernel ipfw source ? (also involves sctp) Message-ID: <slrngr26ef.r98.vadim_nuclight@server.filona.x88.info> References: <20090301153010.GA58942@onelab2.iet.unipi.it> <49AAFD92.105@elischer.org> <8EBEEE24-6473-411D-AE3F-C4D1D3897E51@gmail.com> <alpine.BSF.2.00.0903021827400.11098@fledge.watson.org> <20090302190157.GA33704@onelab2.iet.unipi.it>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Luigi Rizzo! On Mon, 2 Mar 2009 20:01:57 +0100; Luigi Rizzo wrote about 'Re: spliting kernel ipfw source ? (also involves sctp)': >>>>>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 [...] > To further clarify, my plan is the following: > - leave ip_fw.h and ip_dummynet.h in /sys/netinet in case > userland code is dependent on their location; > - create /sys/netinet/ipfw/ to hold the kernel .c files related to > ipfw and possibly dummynet (and also their private headers if any); Exactly that and nothing more? I'm currently working on extending ipfw for Foundation with userland interface will be changed (and I thinking about introducing modules), what else do you plan to do? -- WBR, Vadim Goncharov. ICQ#166852181 mailto:vadim_nuclight@mail.ru [Moderator of RU.ANTI-ECOLOGY][FreeBSD][http://antigreen.org][LJ:/nuclight]
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?slrngr26ef.r98.vadim_nuclight>