Update READMEs for 4.1

git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@7006 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2007-07-30 17:40:00 +00:00
parent 3f8b0ae49c
commit a0f443df38
6 changed files with 27 additions and 13 deletions

View File

@ -1 +1 @@
This is the Shorewall-common Stable 4.0 branch of SVN.
This is the Shorewall-common Development 4.1 branch of SVN.

View File

@ -1 +1 @@
This is the Shorewall-lite Stable 4.0 branch of SVN.
This is the Shorewall-lite Development 4.1 branch of SVN.

View File

@ -1,2 +1,2 @@
This is the Shorewall-perl Stable 4.0 branch of SVN.
This is the Shorewall-perl Development 4.1 branch of SVN.

View File

@ -1 +1 @@
This is the Shorewall-shell Stable 4.0 branch of SVN.
This is the Shorewall-shell Development 4.1 branch of SVN.

View File

@ -24,10 +24,10 @@ href="GnuCopyright.htm" target="_self">GNU Free Documentation
License</a></span>”.<br>
</p>
<p>July 20, 2007</p>
<p>July 30, 2007</p>
<hr style="width: 100%; height: 2px;">
<p><strong>2007-07-27 Shorewall 4.0.1</strong></p>
<p><strong>2007-07-30 Shorewall 4.0.1</strong></p>
<pre>Problems corrected in 4.0.1.
1) The Shorewall Lite installer was producing an empty shorewall-lite
@ -81,6 +81,14 @@ License</a></span>”.<br>
actions and when a log level followed by '!' was used with any
builtin actions.
10) Shorewall-perl was incorrectly rejecting 'min' as a valid unit of
time in rate-limiting specifications.
11) Certain errors occurring during
start/restart/safe-start/safe-restart/try processing could cause
the lockfile to be left behind. This resulted in a 60-second delay
the next time one of these commands was run.
Other changes in Shorewall 4.0.1.
1) A new EXPAND_POLICIES option is added to shorewall.conf. The
@ -89,7 +97,7 @@ Other changes in Shorewall 4.0.1.
Normally, when the SOURCE or DEST columns in shorewall-policy(5)
contains 'all', a single policy chain is created and the policy is
inforced in that chain. For example, if the policy entry is
enforced in that chain. For example, if the policy entry is
#SOURCE DEST POLICY LOG
# LEVEL
@ -113,7 +121,13 @@ Other changes in Shorewall 4.0.1.
all all REJECT info
loc net ACCEPT
</pre>
4) Recent kernels are apparently hard to configure and we have been
seeing a lot of problem reports where the root cause is the lack of
state match support in the kernel. This problem is difficult to
diagnose when using Shorewall-perl so the generated shell program
now checks specifically for this problem and terminates with an
error if the capability doesn't exist.</pre>
<hr style="width: 100%; height: 2px;">
<p><strong>2007-07-20 Shorewall 4.0.0</strong></p>

View File

@ -21,7 +21,7 @@ Sections, with no Front-Cover, and with no Back-Cover Texts. A copy of the
license is included in the section entitled “<a href="GnuCopyright.htm"
target="_self">GNU Free Documentation License</a>”.</p>
<p>2007-07-20</p>
<p>2007-07-30</p>
<hr style="width: 100%; height: 2px;">
<h2>Table of Contents</h2>
@ -103,17 +103,17 @@ Features page</a>.<br>
<h3><a name="Releases"></a>Current Shorewall Releases</h3>
<p style="margin-left: 40px;">The <span style="font-weight: bold;">current
Stable Release</span> version is  4.0.0<br>
Stable Release</span> version is  4.0.1<br>
</p>
<ul style="margin-left: 40px;">
<li>Here are the <a
href="http://www1.shorewall.net/pub/shorewall/4.0/shorewall-4.0.0/releasenotes.txt">release
href="http://www1.shorewall.net/pub/shorewall/4.0/shorewall-4.0.1/releasenotes.txt">release
notes</a> <br>
</li>
<li>Here are the <a
href="http://www1.shorewall.net/pub/shorewall/4.0/shorewall-4.0.0/known_problems.txt">known
href="http://www1.shorewall.net/pub/shorewall/4.0/shorewall-4.0.1/known_problems.txt">known
problems</a> and <a
href="http://www1.shorewall.net/pub/shorewall/4.0/shorewall-4.0.0/errata/">updates</a>.
href="http://www1.shorewall.net/pub/shorewall/4.0/shorewall-4.0.1/errata/">updates</a>.
<p>Read more about the <a href="Shorewall-4.html">Release here</a>.<br>
</p>
</li>