Date: Sat, 25 Mar 2000 20:39:43 -0800 From: Doug Barton <Doug@gorean.org> To: Tom Legg <tjlegg@shore.net> Cc: freebsd-stable@freebsd.org Subject: Re: Minor rc.network bug for 4.0 and ipfw Message-ID: <38DD948F.D6735548@gorean.org> References: <p04310101b5032cb2a0b9@[207.244.92.51]> <38DD87C8.8D8FC976@gorean.org> <p04310101b5033a42d23f@[207.244.92.51]> <38DD8E7B.CA0781BD@gorean.org> <p04310102b50341186e5f@[207.244.92.51]>
next in thread | previous in thread | raw e-mail | index | archive | help
Tom Legg wrote:
> All I'm saying is that an admin that is sophisticated enough to
> compile a custom kernel with IPFW is also sophisticated enough to
> change the rc flag to "YES" when they want the firewall enabled. But
> I "pity the foo" that has to come and adminster a system where
> firewall_enable="NO" in boot up does not mean net.inet.ip.fw.enable=0
Yes, this has been argued ad infinitum. Check the mail archives if
you're interested. What it boils down to is, we like it the way it is,
and we expect people who load the gun to read how not to shoot their
foot with it.
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?38DD948F.D6735548>