From owner-freebsd-stable Wed Sep 15 11:12:24 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc1.sdca.home.com (ha1.rdc1.sdca.home.com [24.0.3.66]) by hub.freebsd.org (Postfix) with ESMTP id B283215322; Wed, 15 Sep 1999 11:12:21 -0700 (PDT) (envelope-from btalbot@ucsd.edu) Received: from ragtop ([24.0.46.246]) by mail.rdc1.sdca.home.com (InterMail v4.01.01.00 201-229-111) with ESMTP id <19990915181221.PEVS29123.mail.rdc1.sdca.home.com@ragtop>; Wed, 15 Sep 1999 11:12:21 -0700 Message-Id: <4.2.0.58.19990915111209.00a799b0@mail.elcjn1.sdca.home.com> X-Sender: btalbot@ekimaphost (Unverified) X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Wed, 15 Sep 1999 11:12:20 -0700 To: tim@iafrica.com.na, "Greg Quinlan" , From: Bryan Talbot Subject: Re: New rc.conf entry question. Cc: In-Reply-To: <99091513391007.09401@310.priebe.alt.na> References: <4.2.0.58.19990914122726.00a802e0@mail.elcjn1.sdca.home.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 04:33 AM 9/15/99 , Tim Priebe wrote: > > This puts all the custom firewall rules into one location that should > never > > be disturbed by an upgrade. I couldn't get around the need to modify the > > rc.firewall file somewhat though to allow for the use of M4. > >I have done the same thing here, but have used a different filter, as the >person that will have to maintain the rules does not know m4. Shold there >be a >firewall_options variable added? Sounds handy. The quiet option could be handled in the same way of course. Or, to put it another way, the quiet option could be used to specify the preprocessor to be used also. -Bryan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message