From owner-freebsd-pf@FreeBSD.ORG Tue Oct 19 15:57:04 2004 Return-Path: Delivered-To: freebsd-pf@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8A64216A50A for ; Tue, 19 Oct 2004 15:57:03 +0000 (GMT) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.177]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2B2C543D2F for ; Tue, 19 Oct 2004 15:57:03 +0000 (GMT) (envelope-from max@love2party.net) Received: from [212.227.126.208] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 1CJwMA-0003FQ-00; Tue, 19 Oct 2004 17:57:02 +0200 Received: from [217.227.158.113] (helo=donor.laier.local) by mrelayng.kundenserver.de with asmtp (TLSv1:RC4-MD5:128) (Exim 3.35 #1) id 1CJwMA-0007sV-00; Tue, 19 Oct 2004 17:57:02 +0200 From: Max Laier To: freebsd-pf@freebsd.org Date: Tue, 19 Oct 2004 17:56:44 +0200 User-Agent: KMail/1.7 References: <200410180101.48611.max@love2party.net> <41752EAC.5060401@fid4.com> In-Reply-To: <41752EAC.5060401@fid4.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2219292.hUv24BsnGq"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200410191756.45707.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de auth:61c499deaeeba3ba5be80f48ecc83056 Subject: Re: Plans for 6-CURRENT and 5-STABLE X-BeenThere: freebsd-pf@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical discussion and general questions about packet filter (pf) List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Oct 2004 15:57:04 -0000 --nextPart2219292.hUv24BsnGq Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tuesday 19 October 2004 17:11, Michael C. Cambria wrote: > Max Laier wrote: > > [deleted] > > > One of the more serious problems we have to address is how (and if) we > > stay in sync with OpenBSD. As far as I understand it is suggested not to > > change any kernel <-> userland API/ABI during a -STABLE cycle. This > > effectively means that we can *not* track OpenBSD releases in -STABLE > > since they tend to change API/ABI a lot. I think, however, that PF as of > > OpenBSD 3.5 (the one we have now as part of 5-STABLE) is already very > > mature and will serve well for the coming <2 years until we will move on > > to 6-STABLE. > > Can there be a port that does track OpenBSD? Those who want to stay > close to OpenBSD on 5-Stable can then use the port. I will try to make it possible to do a cvs co -rRELENG_5 src cvs up -dA src/contrib/pf src/sys/contrib/pf and rebuild to obtain the latest version in a RELENG_5 tree. Building from = a=20 port and thus having to use pf as module is nothing I'd consider a good=20 solution. On a sidenote: I am going to remove security/pf and security/authpf in a=20 couple of weeks. I still see ~100 downloads per day of the *outdated* sourc= es=20 and want to make it a bit harder for people to use this. =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --nextPart2219292.hUv24BsnGq Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBdTk9XyyEoT62BG0RAm4oAJ46QAwtUsQMv0DXDfuy+wcAGfBmwgCeKe5G qO27+yKU/hw99PNT+asU/OM= =Gbqp -----END PGP SIGNATURE----- --nextPart2219292.hUv24BsnGq--