forked from extern/shorewall_code
Revise FAQ 73 to match reality.
Signed-off-by: Tom Eastep <teastep@shorewall.net>
This commit is contained in:
parent
427b14b21d
commit
430cbf310f
12
docs/FAQ.xml
12
docs/FAQ.xml
@ -1970,14 +1970,10 @@ iptables: Invalid argument
|
||||
the init script, <command>stop</command> reverses the effect of
|
||||
<command>start</command>.</para>
|
||||
|
||||
<para>One way to avoid these differences is to install Shorewall from
|
||||
the tarballs available from shorewall.net. This places Shorewall outside
|
||||
of the control of the packaging system and provides consistent behavior
|
||||
between the init scripts and <filename>/sbin/shorewall</filename> (and
|
||||
<filename>/sbin/shorewall-lite</filename>). For more information on the
|
||||
factors involved when deciding whether to use the Debian package, see
|
||||
<ulink url="http://wiki.shorewall.net/wiki/ShorewallOnDebian">this
|
||||
article</ulink>.</para>
|
||||
<para>Beginning with Shorewall 4.4, when the Shorewall tarballs are
|
||||
installed on a Debian (or derivative) system, the
|
||||
<filename>/etc/init.d/shorewall</filename> file is the same as would be
|
||||
installed by the .deb.</para>
|
||||
</section>
|
||||
|
||||
<section id="faq74">
|
||||
|
Loading…
Reference in New Issue
Block a user