From owner-freebsd-current@FreeBSD.ORG Tue Nov 20 17:47:59 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2185CC2F for ; Tue, 20 Nov 2012 17:47:59 +0000 (UTC) (envelope-from break19@gmail.com) Received: from mail-ie0-f182.google.com (mail-ie0-f182.google.com [209.85.223.182]) by mx1.freebsd.org (Postfix) with ESMTP id CFEA18FC16 for ; Tue, 20 Nov 2012 17:47:58 +0000 (UTC) Received: by mail-ie0-f182.google.com with SMTP id s9so3097130iec.13 for ; Tue, 20 Nov 2012 09:47:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=Yicyr2zaGBlzLXeO8n4ahHT2698+Xb7u4eXeURRyiH4=; b=l9wJomnT7WiepHH3oS3F7IjBeEn1oI8v7kx5wpimEBgl3YXWPyUnJQqfDAD5AJtSo3 ovrAX8FZs6My/UmxSC3OY0AueGBmqKudd92+35jvQZEZI1v4smLZCrnl9P5ooDj7f09V CILH+xl0sEWat3w3ZD2plDRBMdmArNQcjwVvsA1kmgC8oG0FzJ0VwSH/Ff03zujyslZg +70OOPPh6tk9upNhow+nel6A4HJzQb8K3m7Ys5ygyTPbsG98TCYHAUJG2vzSVmQW1d6e KoUmx1ocjUtiC26ZoU6tHPsE33L215aVFMVU8XuEk++1ySLH1sqd0nxXJoLSlxgV1Kzy Cakg== Received: by 10.50.190.162 with SMTP id gr2mr10960618igc.65.1353433677914; Tue, 20 Nov 2012 09:47:57 -0800 (PST) Received: from [192.168.0.199] ([173.157.127.48]) by mx.google.com with ESMTPS id px5sm10047002igc.0.2012.11.20.09.47.53 (version=SSLv3 cipher=OTHER); Tue, 20 Nov 2012 09:47:57 -0800 (PST) Message-ID: <50ABC214.9060800@gmail.com> Date: Tue, 20 Nov 2012 11:47:00 -0600 From: Chuck Burns User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: Aldis Berjoza Subject: Re: Upgrading FreeBSD to use the NEW pf syntax. (Copied from freebsd-pf) References: <50ABAF8E.3020101@zedat.fu-berlin.de> <50ABB0C7.7070404@gmail.com> <1023391353430321@web2h.yandex.ru> In-Reply-To: <1023391353430321@web2h.yandex.ru> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Nov 2012 17:47:59 -0000 On 11/20/2012 10:52 AM, Aldis Berjoza wrote: > > > 20.11.2012, 18:34, "Chuck Burns" : >> On 11/20/2012 10:27 AM, O. Hartmann wrote: >> >>> On 11/20/12 11:43, Olivier Smedts wrote: >>>> 2012/11/20 Paul Webster : >>>>> I am aware this is a much discussed subject since the upgrade of PF, I >>>>> believe the final decision was that to many users are used to the old >>>>> style pf and an upgrade to the new syntax would cause to much confusion. >>>> But a change like this is expected in a new major branch, ie. >>>> 10-CURRENT. Not so in -STABLE branches of course. I don't see the >>>> problem here. >>>> >>>> Cheers >>> What would be the alternative? Being stuck with the old PF? As Olivier >>> Smedts said, changes like that are expected in a complete new branch. If >>> people need to stay compatible, they are about to use 9.X as long as >>> they have migrated. The downside is more work. The bright side would be >>> development/progression. >>> >>> oh >> >> Why not release pf2 as a port? Then those who want the new pf can use >> it, and those that want the old one can use it. >> >> Or, another option is a knob USE_NEWPF during buildworld will build the >> new pf, otherwise it'd build the old, default one. >> >> This way you can still introduce the change, but default to the old one >> for those of us who are too crusty to change. :) >> > > FreeBSD already have 3x firewalls. Having 4th m I think, isn't desired. > Nonsense. More options are always preferable to fewer options. -- Chuck Burns