From owner-freebsd-stable Sat Mar 25 20:14: 0 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id 5176D37B879 for ; Sat, 25 Mar 2000 20:13:52 -0800 (PST) (envelope-from Doug@gorean.org) Received: from gorean.org (doug@master [10.0.0.2]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id UAA08293; Sat, 25 Mar 2000 20:13:47 -0800 (PST) (envelope-from Doug@gorean.org) Message-ID: <38DD8E7B.CA0781BD@gorean.org> Date: Sat, 25 Mar 2000 20:13:47 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 5.0-CURRENT-0322 i386) X-Accept-Language: en MIME-Version: 1.0 To: Tom Legg Cc: freebsd-stable@freebsd.org Subject: Re: Minor rc.network bug for 4.0 and ipfw References: <38DD87C8.8D8FC976@gorean.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tom Legg wrote: > In fact the current situation renders the rc.conf flag for > firewall_enable mute. You might as well eliminate the flag and have > /etc/rc.network check whether net.inet.ip.fw.enable=1 and go from > there. I think you mean moot. :) In any case, the current set of options allows a user to specify the settings in rc.conf without compiling the ipfw stuff into the kernel. Doug -- "So, the cows were part of a dream that dreamed itself into existence? Is that possible?" asked the student incredulously. The master simply replied, "Mu." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message