Date: Sun, 28 Jul 2002 19:44:22 -0400 (EDT) From: Munish Chopra <mchopra@engmail.uwaterloo.ca> To: FreeBSD-gnats-submit@FreeBSD.org Subject: docs/41091: customer firewall --> custom firewall Message-ID: <20020728234422.64E2E26D@opiate.thirteenandtwo.org>
next in thread | raw e-mail | index | archive | help
>Number: 41091
>Category: docs
>Synopsis: customer firewall --> custom firewall
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-doc
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: change-request
>Submitter-Id: current-users
>Arrival-Date: Sun Jul 28 16:50:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator: Munish Chopra
>Release: FreeBSD 5.0-CURRENT i386
>Organization:
>Environment:
System: FreeBSD opiate.thirteenandtwo.org 5.0-CURRENT FreeBSD 5.0-CURRENT #7: Sun Jul 21 23:12:09 EDT 2002 munish@CPE0030ab0ef2bb.cpe.net.cable.rogers.com:/usr/src/sys/i386/compile/ARCADIA i386
>Description:
Change 'customer firewall' to 'custom firewall'. Small thing noticed while reading firewall(7).
>How-To-Repeat:
>Fix:
--- /usr/src/share/man/man7/firewall.7 Tue Jun 25 06:17:49 2002
+++ firewall.7 Sun Jul 28 19:41:17 2002
@@ -60,7 +60,7 @@
the packet. We cover these and other quirks involved with constructing
a firewall in the sample firewall section below.
.Sh IPFW KERNEL CONFIGURATION
-You do not need to create a customer kernel to use the IP firewalling features.
+You do not need to create a custom kernel to use the IP firewalling features.
If you enable firewalling in your
.Em /etc/rc.conf
(see below), the ipfw kernel module will be loaded automatically. However,
>Release-Note:
>Audit-Trail:
>Unformatted:
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-doc" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020728234422.64E2E26D>