Link the Shorewall-perl article from the FAQ

git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@5864 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb

docs/FAQ.xml

@@ -1666,10 +1666,10 @@ Creating input Chains...
       will revert to the old configuration stored in
       <filename>/var/lib/shorewall/restore</filename>.</para>
 
-      <para>Finally, the time that new connections are blocked during
+      <para>The time that new connections are blocked during shorewall restart
-      shorewall restart can be dramatically reduced by upgrading to Shorewall
+      can be dramatically reduced by upgrading to Shorewall 3.2 or later. In
-      3.2 or later. In 3.2 and later releases, <command>shorewall
+      3.2 and later releases, <command>shorewall [re]start</command> proceeds
-      [re]start</command> proceeds in two phases:</para>
+      in two phases:</para>
 
       <orderedlist>
         <listitem>
@@ -1683,6 +1683,10 @@ Creating input Chains...
         </listitem>
       </orderedlist>
 
+      <para>Finally, if you are adventuresome, you can try <ulink
+      url="Shorewall-perl.html">Shorewall-perl</ulink>, the new Shorewall
+      compiler currently under development. It is very fast.</para>
+
       <para>For additional information about Shorewall Scalability and
       Performance, see <ulink url="ScalabilityAndPerformance.html">this
       article</ulink>.</para>

docs/Shorewall-perl.xml

@@ -62,6 +62,12 @@
         configuration than the Shorewall-shell compiler does.</para>
       </listitem>
 
+      <listitem>
+        <para>The error messages produced by the compiler are better, more
+        consistent and always include the file name and line number where the
+        error was detected.</para>
+      </listitem>
+
       <listitem>
         <para>Going forward, the Shorewall-perl compiler will get all
         enhancements; the Shorewall-shell compiler will only get those

docs/XenMyWay-Routed.xml

@@ -187,11 +187,11 @@
         that boots Xen in Dom0.</para>
 
         <blockquote>
-          <programlisting>title XEN
+          <programlisting>title Kernel-2.6.18.8-0.1-xen
-    root (hd0,1)
+    root (hd0,5)
-    kernel /boot/xen.gz Dom0_mem=458752 sched=bvt
+    kernel /boot/xen.gz 
-    module /boot/vmlinuz-xen root=/dev/hda2 vga=0x31a selinux=0    resume=/dev/hda1  splash=silent showopts 
+    module /boot/vmlinuz-2.6.18.8-0.1-xen root=/dev/sda6 vga=0x31a resume=/dev/sda5 splash=silent showopts
-    module /boot/initrd-xen</programlisting>
+    module /boot/initrd-2.6.18.8-0.1-xen</programlisting>
         </blockquote>
 
         <para><filename>/etc/modprobe.conf.local</filename> (This may need to
@@ -208,29 +208,19 @@
         automatically by Xen's <emphasis>xendomains</emphasis> service.</para>
 
         <blockquote>
-          <programlisting>#  -*- mode: python; -*-
+          <programlisting>disk = [ 'phy:/dev/sda9,hda,w', 'phy:/dev/hda,hdb,r' ]
-
-# configuration name:
-name     = "lists"
-
-# usable ram:
 memory = 512
-
+vcpus = 1
-# kernel and initrd:
+builder = 'linux'
-kernel   = "/xen2/vmlinuz-xen"
+name = 'server'
-ramdisk  = "/xen2/initrd-xen"
+vif = [ 'mac=00:16:3e:b1:d7:90, <emphasis role="bold">ip=206.124.146.177, vifname=eth3</emphasis>' ]
-
+localtime = 0
-# boot device:
+on_poweroff = 'destroy'
-root     = "/dev/hda3"
+on_reboot = 'restart'
-
+on_crash = 'restart'
-# boot to run level:
+extra = ' TERM=xterm'
-extra    = "3"
+bootloader = '/usr/lib/xen/boot/domUloader.py'
-
+bootentry = 'hda2:/boot/vmlinuz-xen,/boot/initrd-xen'</programlisting>
-# network interface:
-vif      = [ 'mac=aa:cc:00:00:00:01, <emphasis role="bold">ip=206.124.146.177, vifname=eth3</emphasis>' ]
-
-# storage devices:
-disk     = [ 'phy:hda3,hda3,w' ]</programlisting>
 
           <para>Note that the vifname is set to 'eth3' for the virtual
           interface to this DomU. This will cause the Dom0 interface to the
@@ -293,32 +283,22 @@ gateway:~ #</programlisting>
         <note>
           <para>I have been asked a couple of times "How would I add another
           domU to the DMZ?" Here is a sample config file to add a second domU
-          named "server", boot device <filename>/dev/hdb1</filename> and IP
+          named "server", boot device <filename>/dev/sda10</filename> and IP
           address 206.124.146.179:</para>
 
-          <programlisting>#  -*- mode: python; -*-
+          <programlisting>disk = [ 'phy:/dev/sda10,hda,w', 'phy:/dev/hda,hdb,r' ]
-
-# configuration name:
-name     = "server"
-
-# usable ram:
 memory = 512
-
+vcpus = 1
-# kernel and initrd:
+builder = 'linux'
-kernel   = "/xen2/vmlinuz-xen"
+name = 'server'
-ramdisk  = "/xen2/initrd-xen"
-
-# boot device:
-root     = "/dev/hdb1"
-
-# boot to run level:
-extra    = "3"
-
-# network interface:
 vif = [ 'mac=aa:cc:00:00:00:02, <emphasis role="bold">ip=206.124.146.179, vifname=eth4</emphasis>' ]
-
+localtime = 0
-# storage devices:
+on_poweroff = 'destroy'
-disk     = [ 'phy:hdb1,hdb1,w' ]</programlisting>
+on_reboot = 'restart'
+on_crash = 'restart'
+extra = ' TERM=xterm'
+bootloader = '/usr/lib/xen/boot/domUloader.py'
+bootentry = 'hda2:/boot/vmlinuz-xen,/boot/initrd-xen'</programlisting>
 
           <para>Note that this domU has its own vif named <filename
           class="devicefile">eth4</filename>.</para>