Date: Mon, 10 May 2004 02:28:29 -0700 (PDT) From: Giorgos Keramidas <keramida@ceid.upatras.gr> To: freebsd-gnats-submit@FreeBSD.org Subject: docs/66442: [PATCH] proposed dialup-firewall article wording change Message-ID: <200405100928.i4A9STqI041982@www.freebsd.org> Resent-Message-ID: <200405100930.i4A9UGfU046077@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 66442
>Category: docs
>Synopsis: [PATCH] proposed dialup-firewall article wording change
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-doc
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: doc-bug
>Submitter-Id: current-users
>Arrival-Date: Mon May 10 02:30:16 PDT 2004
>Closed-Date:
>Last-Modified:
>Originator: Giorgos Keramidas
>Release: 5-CURRENT
>Organization:
>Environment:
>Description:
Both paragraphs listed in the diff below start with "First". Surely one of them must be "second" :-)
The rewording is probably suboptimal, but if anyone has a better idea about a way to keep the changes minimal and avoid repeatedly using the same word (First), go for it.
>How-To-Repeat:
>Fix:
%%
--- article.sgml.orig 2004-05-10 10:34:03.000000000 +0300
+++ article.sgml.new 2004-05-10 10:33:54.000000000 +0300
@@ -161,17 +161,17 @@
<para>First, let's start with the basics of closed firewalling.
Closed firewalling is based on the idea that everything is denied
by default. The system administrator may then explicitly add
rules for traffic that he or she would like to allow. Rules
should be in the order of allow first, and then deny. The premise
is that you add the rules for everything you would like to allow,
and then everything else is automatically denied.</para>
- <para>First off, let's create the directory where we will store our
+ <para>Following that, let's create the directory where we will store our
firewall rules. In this example, we'll use <filename
class="directory">/etc/firewall</filename>. Change into the
directory and edit the file <filename>fwrules</filename> as we
specified in <filename>rc.conf</filename>. Please note that you
can change this filename to anything you wish. This guide merely
gives an example of a filename you may want to use.</para>
<para>Now, let's look at a nicely commented sample firewall
%%
>Release-Note:
>Audit-Trail:
>Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200405100928.i4A9STqI041982>