From owner-freebsd-stable Mon Jan 28 16:34:10 2002 Delivered-To: freebsd-stable@freebsd.org Received: from sage-american.com (sage-american.com [216.122.141.44]) by hub.freebsd.org (Postfix) with ESMTP id B613537B402 for ; Mon, 28 Jan 2002 16:34:04 -0800 (PST) Received: from SAGEONE (adsl-64-219-20-214.dsl.crchtx.swbell.net [64.219.20.214]) by sage-american.com (8.9.3/8.9.3) with SMTP id SAA07080; Mon, 28 Jan 2002 18:33:34 -0600 (CST) Message-Id: <3.0.5.32.20020128183332.01831ca0@mail.sage-american.com> X-Sender: jacks@mail.sage-american.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Mon, 28 Jan 2002 18:33:32 -0600 To: Patrick Greenwell , Matthew Whelan From: jacks@sage-american.com Subject: Re: Proposed Solution To Recent "firewall_enable" Thread. [Please Read] Cc: "M. Warner Losh" , Nate Williams , , , In-Reply-To: <20020128155135.X342-100000@rockstar.stealthgeeks.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Patrick: I truly believe you started a good thread that has certainly gained attention to something I suspect will be treated some day and no doubt -current is the place to start it. I never got into trouble with a lock out with this issue, but was just lucky methinks.... I certainly was doing a degree of guessing initially with the rc after compiling FW into the kernel. But, I set the rc to "open" figuring that would at least keep letting me in while tweaking the rules... Sure those that already know what it does have no problem one way or another, but many more newbies are lined up at the gate.... so who should be bothered the oldies or the newbies...? Wasn't everyone a newbie at some time...? (I didn't mean you JC!) At 03:55 PM 1.28.2002 -0800, Patrick Greenwell wrote: >On Mon, 28 Jan 2002, Matthew Whelan wrote: > >> Isn't this starting to get a bit big a change for -STABLE? (unless you have >> an interim rc.network that understands both the old and new, translates old >> to new, and flashes a big warning that you change, or something :) > >My fault for opening this can of worms on -stable. The discussion/proposed >changes probably do belong on -current. I've just never run a -CURRENT >system and don't subscribe to -current... > > >/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ \/\ > Patrick Greenwell > Stealthgeeks,LLC. Operations Consulting > http://www.stealthgeeks.net >\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\ /\/ > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-stable" in the body of the message > > Best regards, Jack L. Stone, Server Admin =================================================== Sage-American http://www.sage-american.com jacks@sage-american.com "My center is giving way, my right is in retreat; ....situation excellent! ....I shall attack!" =================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message