Subject: Re: src/etc imports for PF
To: Jun-ichiro itojun Hagino <itojun@itojun.org>
From: Luke Mewburn <lukem@NetBSD.org>
List: tech-userlevel
Date: 06/29/2004 17:53:20
--gDjY2bUXmwR4focy
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Tue, Jun 29, 2004 at 04:41:26PM +0900, Jun-ichiro itojun Hagino wrote:
| > Hi Itojun.
| >=20
| > For consistency with the way that we're moving to maintain other
| > third party software in our tree, could you please:
|=20
| question: consistency with what? is there any written description,
| or is it your personal preference/rule? i don't see any prior art on
| this "consistency" thing, so i have no motivation/justification to
| follow your recommendation. anyways, here are my comments. i won't
| bother to commit/re-import.
Consistency with at least the following 3rd party products:
amd
bind
dhcp
ipf
ntp
postfix
sendmail
That is _significant_ prior art in our tree for this type of software.
| > 1. Reimport
| > pf.os
| > pf.conf
| > spamd.conf
| > into=20
| > dist/pf/examples
|=20
| pf.os is OS fingerprint database, therefore I really want to keep it
| in /etc (just like /etc/moduli used by ssh).
Well, it will need a special handling if we implement
MKIPFILTER/MKPF method proposed in a PR (by Peter Postma ?)
| > 3. Reimport
| > pflog.4
| > pf.4
| > pf.os.5
| > pf.conf.5
| > spamd.conf.5
| > into
| > dist/pf/man
| > and remove them from
| > share/man/man[45]
| >=20
| > Create a reachover Makefiles under
| > usr.sbin/pf/man
| > to install these manual pages
| >=20
| >=20
| > 4. Relocate the following directories
| > sbin/pfctl -> usr.sbin/pf/pfctl
| > libexec/ftp-proxy -> usr.sbin/pf/ftp-proxy
| > libexec/spamd -> usr.sbin/pf/spamd
| > libexec/spamd-setup -> usr.sbin/pf/spamd-setup
| > libexec/spamlogd -> usr.sbin/pf/spamlogd
| > usr.sbin/authpf -> usr.sbin/pf/authpf
| > usr.sbin/spamdb -> usr.sbin/pf/spamdb
| > (even though they can still be installed in the
| > same /sbin, /usr/libexec & /usr/sbin locations)
|=20
| i do not see benefit of 3 and 4. 4 is just for confuse people
| work on PF source code.
Besides the consistency with other 3rd party tools in our tree,
it also makes it far easier to implement a MKPF build switch.
--gDjY2bUXmwR4focy
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (NetBSD)
iD8DBQFA4R/wpBhtmn8zJHIRAmIzAJ9QD9fVRWftlM/WCwDQKB1I2qvu6ACdE+l6
kd6dTNNkW/HG2BaDA0cUVwI=
=Cmdd
-----END PGP SIGNATURE-----
--gDjY2bUXmwR4focy--