Added netconfig and startup services section to ch02

Made minor changes to ch14 15 16

5 files changed, 231 insertions, 137 deletions

diff --git a/TODO b/TODO
index 7d96c0f..91f61c0 100644
--- a/TODO
+++ b/TODO
@@ -28,10 +28,6 @@ Chapter 10. Working with Filesystems
   allows you to find out exactly what NFS exports a remote server has made 
   available.
 
-Chapter 14. Networking
-
-* Add netconfig.  This is mandatory!
-
 Chapter 16. Basic Networking Commands
 
 * Additional tools to discuss: finger, host, dig, nail
diff --git a/chapter_02.xml b/chapter_02.xml
index 961aca5..885080f 100644
--- a/chapter_02.xml
+++ b/chapter_02.xml
@@ -2,7 +2,7 @@
 <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
   "/usr/share/xml/docbook/xml-dtd-4.5/docbookx.dtd">
 
-<chapter>
+<chapter id="ch_install">
 <title>Installation</title>
 
 <para>
@@ -28,7 +28,7 @@ or from a network card that support PXE. The files there are the best
 source of information available for such boot methods.
 </para>
 
-<section>
+<section id="install_boot">
 <title>Booting the Installer</title>
 
 <para>
@@ -142,7 +142,7 @@ need to do so and should proceed directly to partitioning.
 
 </section>
 
-<section>
+<section id="install_part">
 <title>Partitioning</title>
 
 <para>
@@ -300,7 +300,8 @@ Units = cylinders of 16065 * 512 = 8225280 bytes
 
 </screen>
 
-<para>The swap partition is a special partition that is used for
+<para>
+The swap partition is a special partition that is used for
 virtual memory by the Linux kernel.  If for some reason you run out of
 RAM, the kernel will move the contents of some of the RAM to swap in
 order to prevent a crash.  The size of your swap partition is up to
@@ -353,7 +354,7 @@ ensure that they are properly read by the kernel.
 
 </section>
 
-<section>
+<section id="install_setup">
 <title>The <application>setup</application> Program</title>
 
 <para>
@@ -369,7 +370,7 @@ step-by-step. In order to do so, just type
   <imagedata fileref="png/setup-program.png" format="PNG"/>
 </imageobject>
 
-  <section>
+  <section id="install_setup_help">
   <title>Help</title>
 
   <para>
@@ -384,9 +385,9 @@ step-by-step. In order to do so, just type
     <imagedata fileref="png/setup-help.png" format="PNG"/>
   </imageobject>
 
-  </section>
+  </section> <!-- closing HELP -->
 
-  <section>
+  <section id="install_setup_keymap">
   <title>Keymap</title>
 
   <para>
@@ -404,7 +405,7 @@ step-by-step. In order to do so, just type
 
   </section>
 
-  <section>
+  <section id="install_setup_addswap">
   <title>Addswap</title>
 
   <para>
@@ -425,7 +426,7 @@ step-by-step. In order to do so, just type
   </imageobject>
   </section>
 
-  <section>
+  <section id="install_setup_target">
   <title>Target</title>
 
   <para>
@@ -446,7 +447,7 @@ step-by-step. In order to do so, just type
 
   </section>
 
-  <section>
+  <section id="install_setup_source">
   <title>Source</title>
 
   <para>
@@ -469,7 +470,7 @@ step-by-step. In order to do so, just type
   </imageobject>
   </section>
 
-  <section>
+  <section id="install_setup_select">
   <title>Select</title>
 
   <para>
@@ -490,7 +491,7 @@ step-by-step. In order to do so, just type
   </imageobject>
   </section>
 
-  <section>
+  <section id="install_setup_install">
   <title>Install</title>
 
   <para>
@@ -534,7 +535,7 @@ step-by-step. In order to do so, just type
 
   </section>
 
-  <section>
+  <section id="install_setup_config">
   <title>Configure</title>
 
   <para>
@@ -605,32 +606,119 @@ step-by-step. In order to do so, just type
   </imageobject>
 
   <para>
-  netconfig!
-  FILL THIS IN!!!!!!
-  FILL THIS IN!!!!!!
-  FILL THIS IN!!!!!!
-  FILL THIS IN!!!!!!
-  FILL THIS IN!!!!!!
-  FILL THIS IN!!!!!!
-  FILL THIS IN!!!!!!
-  FILL THIS IN!!!!!!
-  FILL THIS IN!!!!!!
-  FILL THIS IN!!!!!!
-  FILL THIS IN!!!!!!
+    The next stage in configuring your install is the network
+    configuration. If you don't wish to configure your network at this
+    stage, you may decline, but otherwise you'll be prompted to
+    provide a hostname for your computer. Do not enter a domain name,
+    only the hostname.
+  </para>
+
+  <para>
+    The following screen will prompt you for a domainname, such as
+    example.org. The combination of the hostname and the domainname
+    can be used to navigate between computers in your network if you
+    use an internal DNS service or maintain your
+    <filename>&#47;etc&#47;hosts</filename> file.
+  </para>
+
+  <para>
+    You have three options when setting your IP address; you may
+    assign it a static IP, or you may use DHCP, or you may configure a
+    loopback connection. The simplest option, and probably the most
+    common for laptops or computers on a basic network, is to let a
+    DHCP server assign IP addresses dynamically. In practice, this
+    often results in a consistent address since both
+    <application>dhcpcd</application> and
+    <application>dhclient</application> initially request the same
+    address previously assigned. If the address is unavailable then
+    the machine gets a new one, but on small networks this may never
+    happen.
+  </para>
+
+  <para>
+    If the DHCP server on your network requires a specific DHCP
+    hostname before you're permitted to connect. You can enter this on
+    the <guilabel>Set DHCP Hostname</guilabel> screen.
+  </para>
+
+  <para>
+    To use a static IP address, you must provide:
+  </para>
+
+  <variablelist>
+    <title>Static IP Address</title>
+
+    <varlistentry>
+      <term>IP Address</term>
+      <listitem>
+	<para>
+	  The address of your computer, such as 192.168.1.1 (for
+	  IPv4). Also, you should verify that no DHCP server on your
+	  network is set to assign that same address out as a part of
+	  its DHCP pool, or you may encounter address conflicts.
+	</para>
+      </listitem>
+    </varlistentry>
+
+    <varlistentry>
+      <term>Netmask</term>
+      <listitem>
+	<para>
+	  The subnet mask for your network; often 255.255.255.0 for
+	  small networks.
+	</para>
+      </listitem>
+    </varlistentry>
+
+    <varlistentry>
+      <term>Gateway Address</term>
+      <listitem>
+	<para>
+	  The address of the gateway server providing internet access
+	  to your network. On small networks, this will probably be
+	  provided by your ISP while on larger networks you may use an
+	  internal server which handles the traffic. In other words,
+	  this may be an internal address like 192.168.1.1 or it might
+	  be an address provided by your ISP, such as 75.146.49.79
+	</para>
+      </listitem>
+    </varlistentry>
+
+    <varlistentry>
+      <term>Nameserver</term>
+      <listitem>
+	<para>
+	  Most likely, you'll want to utilize DNS; in this initial
+	  setup, provide your primary domain name server. Edit
+	  <filename>&#47;etc&#47;resolv.conf</filename> to add
+	  secondary and tertiary servers later.
+	</para>
+      </listitem>
+    </varlistentry>
+  </variablelist>
+
+  <para>
+    The final screen during static IP address configuration is a
+    confirmation screen, where you're permitted to accept your
+    choices, edit them, or even restart the IP address configuration
+    in case you decide to use DHCP instead.
+  </para>
+
+  <para>
+    Your network configuration is now complete. The next screen
+    prompts you to configure the startup services that you wish to run
+    automatically upon boot. Read the descriptions that appear both to
+    the right of the service name as well as at the bottom of the
+    screen in order to decide whether that service should be turned on
+    by default. These can always be modified later with
+    <application>pkgtool</application> &#62; <guimenu>Setup</guimenu>
+    &#62; <guimenuitem>Services</guimenuitem>.
   </para>
 
   <para>
-  services!
-  FILL THIS IN!!!!!!
-  FILL THIS IN!!!!!!
-  FILL THIS IN!!!!!!
-  FILL THIS IN!!!!!!
-  FILL THIS IN!!!!!!
-  FILL THIS IN!!!!!!
-  FILL THIS IN!!!!!!
-  FILL THIS IN!!!!!!
-  FILL THIS IN!!!!!!
-  FILL THIS IN!!!!!!
+    As the startup services window warns, you should only turn on the
+    startup services that you actually intend to use. This not only
+    decreases boot time but makes for a more secure system.
   </para>
 
   <para>
diff --git a/chapter_14.xml b/chapter_14.xml
index b9e7e58..aeedd11 100644
--- a/chapter_14.xml
+++ b/chapter_14.xml
@@ -2,10 +2,10 @@
 <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
   "/usr/share/xml/docbook/xml-dtd-4.5/docbookx.dtd">
 
-<chapter id="ch_networking">
+<chapter id="ch_network">
 <title>Networking</title>
 
-<section id="sect_netconfig">
+<section id="network_netconfig">
 <title><application>netconfig</application></title>
 
 <para>
@@ -43,24 +43,23 @@ book.
 
 </section>
 
-<section id="sect_manual-configuration">
+<section id="network_manual-configuration">
 <title>Manual Configuration</title>
 
 <para>
 Ok, so you've installed Slackware, you've setup a desktop, but you
 can't get it to connect to the Internet or your business's LAN (local
-area network), what do you do? Fortunately, the answer to that question
-is simple. Slackware includes a number of tools to configure your
-network connection. The first we will look at today is the very
-powerful <application>ifconfig</application>(8).
-<application>ifconfig</application> is used to setup or modify the
-configuration of a Network Interface Card (NIC or Ethernet Card), the
-most common hardware for connecting to networks today.
-<application>ifconfig</application> is an incredibly powerful tool
-capable of doing much more than setting IP addresses. For a complete
-introduction, you should read its man page. For now, we're just going
-to use it to display and change the network addresses of some ethernet
-controllers.
+area network), what do you do? Fortunately, the answer to that
+question is simple. Slackware includes a number of tools to configure
+your network connection. The first we will look at is the very
+powerful <application>ifconfig</application>(8), which is used to
+setup or modify the configuration of the most common hardware for
+connecting to networks: a Network Interface Card (NIC or
+Ethernet Card). <application>ifconfig</application> is an incredibly powerful
+tool capable of doing much more than setting IP addresses. For a
+complete introduction, you should read its man page. For now, we're
+just going to use it to display and change the network addresses of
+some ethernet controllers.
 </para>
 
 <screen><prompt>darkstar:~&#35; </prompt><userinput>ifconfig</userinput>
@@ -177,7 +176,8 @@ For now, let's take a look at our routing table immediately after
 setting up eth0.
 </para>
 
-<screen><prompt>darkstar:~&#35; </prompt><userinput>route</userinput>
+<screen>
+<prompt>darkstar:~&#35; </prompt><userinput>route</userinput>
 Kernel IP routing table
 Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
 192.168.1.0     *               255.255.255.0   U     0      0        0 eth0
@@ -198,7 +198,8 @@ itself.  In order to reach the rest of the world, we'll need to
 setup a default gateway.
 </para>
 
-<screen><prompt>darkstar:~&#35; </prompt><userinput>route add default gw 192.168.1.254</userinput>
+<screen>
+<prompt>darkstar:~&#35; </prompt><userinput>route add default gw 192.168.1.254</userinput>
 <prompt>darkstar:~&#35; </prompt><userinput>route</userinput>
 Kernel IP routing table
 Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
@@ -233,7 +234,7 @@ nameserver 192.168.1.254
 </screen>
 
 <para>
-Most users won't need the <parameter>search</parameter> line. This is used to map hostnames
+Many users won't need the <parameter>search</parameter> line. This is used to map hostnames
 to domain names. Basically, if I attempt to connect to "barnowl", the
 computer knows to look for "barnowl.lizella.net" thanks to this search
 line. We're mainly interested in the <parameter>nameserver</parameter> line. This tells
@@ -305,7 +306,7 @@ clients, so use whichever you prefer.
 
 </section>
 
-<section id="sect_automatic-configuration">
+<section id="network_automatic-configuration">
   <title>
     Automatic Configuration with <filename>rc.inet1.conf</filename>
   </title>
@@ -357,14 +358,17 @@ Protocol Address for the <varname>n</varname> network interface card.
 Typically, <varname>n</varname> corrosponds to
 <parameter>eth0</parameter>, <parameter>eth1</parameter>, and so on,
 but this isn't always the case.  You can specify these values to
-pertain to a different network controller with the INFAME&#91;n&#93;
-variable, but we will reserve that for the next chapter on wireless
-networking, as it more commonly pertains to wireless network
-controllers. Likewise, NETMASK&#91;n&#93; is the subnet mask to use
-for the network controller.  If these lines are left empty, then
-static IP addresses will not be automatically assigned to this network
-controller.  The <varname>USE_DHCP&#91;n&#93;</varname> variable tells
-Slackware &#40;naturally&#41; to use DHCP to configure the interface.
+pertain to a different network controller with the IFNAME&#91;n&#93;
+variable, but we will reserve that for <xref linkend="ch_wireless"/>,
+as it more commonly pertains to wireless network controllers.
+</para>
+
+<para>
+Likewise, NETMASK&#91;n&#93; is the subnet mask to use for the network
+controller.  If these lines are left empty, then static IP addresses
+will not be automatically assigned to this network controller.  The
+<varname>USE_DHCP&#91;n&#93;</varname> variable tells Slackware
+&#40;naturally&#41; to use DHCP to configure the interface.
 <varname>DHCP_HOSTNAME&#91;n&#93;</varname> is rarely used, but some
 DHCP servers may require it.  In that case, it must be set to a valid
 hostname. Finally, we come to the GATEWAY variable.  It is actually
@@ -379,13 +383,14 @@ interfaces are attached to it.
 
 <para>
 If you need to use static IP addressing, you will have to obtain a
-unique static IP address and the subnet mask for the interface, as well
-as the default gateway address, and enter those here. There is no place
-to enter DNS information in <filename>rc.inet1.conf</filename>, so DNS
-servers will have to be manually placed into
-<filename>resolv.conf</filename> as we discussed above. Of course, if
-you use <application>netconfig</application>, this will be handled for
-you by that program.  Now let's take a look at another interface on my
+unique static IP address and the subnet mask for the interface, as
+well as the default gateway address, and enter those here. There is no
+place to enter DNS information in <filename>rc.inet1.conf</filename>,
+so DNS servers will have to be manually placed into
+<filename>resolv.conf</filename> as discussed in <xref
+linkend="network_manual-configuration"/>. Of course, if you use
+<application>netconfig</application>, this will be handled for you by
+that program.  Now let's take a look at another interface on my
 computer.
 </para>
 
diff --git a/chapter_15.xml b/chapter_15.xml
index e7d0cc4..0e80bbc 100644
--- a/chapter_15.xml
+++ b/chapter_15.xml
@@ -2,10 +2,10 @@
 <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
   "/usr/share/xml/docbook/xml-dtd-4.5/docbookx.dtd">
 
-<chapter id="ch_wireless-networking">
+<chapter id="ch_wireless">
 <title>Wireless Networking</title>
 
-<section id="sect_iwconfig">
+<section id="wireless_iwconfig">
   <title>
     <application>iwconfig</application>
   </title>
@@ -46,24 +46,29 @@ tun0      no wireless extensions.
 <para>
 Unlike wired networks, wireless networks are &#34;fuzzy&#34;. Their borders are
 hard to define, and multiple networks may overlap one another. In order
-to avoid confusion, each wireless network has &#34;hopefully&#41; unique
+to avoid confusion, each wireless network has &#40;hopefully&#41; unique
 identifiers. The two most basic identifiers are the Extended Service
 Set Identifier &#40;ESSID&#41; and the channel or frequency for radio
 transmission. The ESSID is simply a name that identifies the wireless
-network in question; you may have heard it referred to as the network
-name or something similar. Typical wireless networks operate on 11
-different frequencies. In order to connect to even the most basic
-wireless network, you will have to setup these two pieces of
-information, and possibly others, before setting up things like the
-WNIC's IP address. Here you can see that my ESSID is set to "nest" and
-my laptop is transmitting at 2.432 GHz. This is all that is required to
-connect to an unencrypted wireless LAN. &#40;For any of you out there
-expecting to come to my house and use my unencrypted wireless, you
-should know that you'll have to break a 2048-bit SSL key before the
-access point will let you communicate with my LAN.&#41;
+network in question; you may have heard it referred to as the &#34;network
+name&#34; or something similar. 
 </para>
 
-<screen><prompt>darkstar:~&#35; </prompt><userinput>iwconfig wlan0 essid nest \
+<para> 
+Typical wireless networks operate on 11 different frequencies. In
+order to connect to even the most basic wireless network, you will
+have to setup these two pieces of information, and possibly others,
+before setting up things like the WNIC's IP address. Here you can see
+that my ESSID is set to &#34;nest&#34; and my laptop is
+transmitting at 2.432 GHz. This is all that is required to connect to
+an unencrypted wireless LAN. &#40;For any of you out there expecting
+to come to my house and use my unencrypted wireless, you should know
+that you'll have to break a 2048-bit SSL key before the access point
+will let you communicate with my LAN.&#41;
+</para>
+
+<screen>
+  <prompt>darkstar:~&#35; </prompt><userinput>iwconfig wlan0 essid nest \
   freq 2.432G</userinput></screen>
 
 <para>
@@ -73,17 +78,19 @@ frequency or channel to use, Slackware can usually figure this out for
 you.
 </para>
 
-<screen><prompt>darkstar:~&#35; </prompt><userinput>iwconfig wlan0 essid nest \
-  channel auto</userinput></screen>
+<screen>
+  <prompt>darkstar:~&#35; </prompt><userinput>iwconfig wlan0 essid nest \
+  channel auto</userinput>
+</screen>
 
 <para>
 Now Slackware will attempt to connect to the strongest access point on
-the "nest" essid operating at any frequency.
+the &#34;nest&#34; essid operating at any frequency.
 </para>
 
 </section>
 
-<section id="sect_wep">
+<section id="wireless_wep">
 <title>Wired Equivilant Protection (or Lack Thereof)</title>
 
 <para>
@@ -105,7 +112,8 @@ you'll need to prepend it with &#34;s&#59;&#34; but generally
 speaking, hexidecimal format is preferred.
 </para>
 
-<screen><prompt>darkstar:~&#35; </prompt><userinput>iwconfig wlan0 \
+<screen>
+<prompt>darkstar:~&#35; </prompt><userinput>iwconfig wlan0 \
   key cf80baf8bf01a160de540bfb1c</userinput>
 <prompt>darkstar:~&#35; </prompt><userinput>iwconfig wlan0 \
   key s:thisisapassword</userinput>
@@ -113,7 +121,7 @@ speaking, hexidecimal format is preferred.
 
 </section>
 
-<section id="sect_wpa">
+<section id="wireless_wpa">
 <title>Wifi Protected Access</title>
 
 <para>
@@ -173,20 +181,26 @@ course, this is a lot of work; there must be an easier way to do this.
 
 <!-- not closing this yet /section -->
 
-<section id="sect_rcinet1conf-revisited">
+<section id="wireless_rcinet1conf-revisited">
 <title>rc.inet1.conf revisited</title>
 
 <para>
-Welcome back to <filename>rc.inet1.conf</filename>.  You're recall in
-the last chapter that we used this configuration file to automatically
-configure NICs whenever Slackware boots.  Now, we will use it to
-configure wifi as well.  If you're using WPA2, you'll still need to
-setup <filename>wpa_supplicant.conf</filename> properly first, however.
+Welcome back to <filename>rc.inet1.conf</filename>.  You're recall
+that in <xref linkend="ch_network"/> we used this configuration file
+to automatically configure NICs whenever Slackware boots.  Now, we
+will use it to configure wifi as well.
 </para>
 
+<note>
+  <para>
+    If you're using WPA2, you'll still need to setup
+    <filename>wpa_supplicant.conf</filename> properly first, however.
+  </para>
+</note>
+
 <para>
 Recall that each NIC had a name or number that identified the variables
-that corrospond with it?  The same hold true for wifi NICs, only they
+that correspond with it?  The same hold true for wifi NICs, only they
 have even more variables due to the added complexity of wireless
 networking.
 </para>
@@ -227,7 +241,7 @@ other than <varname>ethn</varname> and that is reflected here.  When
 <filename>rc.inet1.conf</filename> is read by the start-up scripts,
 Slackware knows to apply all these options to the <varname>wlan0</varname> wifi NIC
 instead of the &#40;probably non-existant&#41; eth4 wired NIC.  Many of the
-other options are the same.  IP address information is added in
+other options are the same. IP address information is added in
 exactly the same way we discussed for wired network cards in <xref
 linkend="ch_networking"/>; however, we have a lot of new variables that need
 some explanation.
@@ -264,7 +278,7 @@ absolutely correct.
 
 </section> <!-- closing WPA discussion -->
 
-<section id="sect_wicd">
+<section id="wireless_wicd">
   <title>wicd</title>
 
 <para>
@@ -328,34 +342,19 @@ from either the KDE or XFCE menu.
 
 <para>
   Optionally, you could manually run
-<application>wicd-client</application>(1) from a terminal or run
-dialogue.
+<application>wicd-client</application>(1) from a terminal or <application>run
+dialogue</application>.
 </para>
 
 <para>
-  If you're not running <application>X</application> or simply would
-  prefer to stay in the terminal, you can launch the command line
-  version, <application>wicd-curses</application>.
-</para>
-
-  <mediaobject>
-    <imageobject>
-      <imagedata
-	  fileref="./img/wicd-curses.png" format="PNG" />
-    </imageobject>
-    <textobject>
-      <phrase>The wicd-curses interface</phrase>
-    </textobject>
-  </mediaobject>
-
-<para>
   On the graphical front-end, options for different networks are
   available via the <guibutton>Preferences</guibutton> button adjacent
   to the ESSID listed. In the terminal client, the same options can be
-  reached by highlighting the network you wish to configure and
-  pressing <keycap>c</keycap>.
+  reached by highlighting the ESSID you wish to use and
+  pressing the right arrow key, which opens a configuration page for
+  that network.
 </para>
 
 </section> <!-- closing wicd section -->
 
-</chapter>
+</chapter>
\ No newline at end of file
diff --git a/chapter_16.xml b/chapter_16.xml
index 97a0fee..05a32e0 100644
--- a/chapter_16.xml
+++ b/chapter_16.xml
@@ -433,9 +433,9 @@ A more feature-rich alternative is the popular
 <application>links</application>(1), a console-based web browser that
 supports frames and has better table rendering than
 <application>lynx</application>. Like its predecessor,
-<application>links</application> is navigated with the arrow keys, and
-the use of a mouse is supported.  Unlike,
-<application>lynx</application> it also includes a handy menu (simply
+<application>links</application> is navigable with the arrow keys, and
+the use of a mouse is supported.  Unlike
+<application>lynx</application>, it also includes a handy menu (simply
 click on the top line with your mouse to activate) and generally
 formats web pages better.
 </para>
@@ -729,7 +729,7 @@ for that, muttrc(5). You might want to read up on it.
 
   <listitem>
     <para>
-      <command>formail</command> to re-format your mail if needed
+      Optionally, <command>formail</command> to re-format your mail if needed
       &#40;depending on your mail server settings&#41;
     </para>
 </listitem>
@@ -822,9 +822,10 @@ here and wants mds "/usr/bin/procmail"&#39; &#62;&#62; ~&#47;.fetchmailrc
 </variablelist>
 
 <para>
-  Now that fetchmail is configured, it will successfully pull your
-  email from the server.  But what will your computer do with all of
-  that mail?  This is the job of <application>procmail</application>.
+  Now that <application>fetchmail</application> is configured, it will
+  successfully pull your email from the server.  But what will your
+  computer do with all of that mail?  This is the job of
+  <application>procmail</application>.
 </para>
 
 <para>
@@ -850,8 +851,8 @@ here and wants mds "/usr/bin/procmail"&#39; &#62;&#62; ~&#47;.fetchmailrc
 <para>
   At this point, your email will be pulled from the server by
   <application>fetchmail</application> and sorted on your local system
-  by way of <application>procmail</application>.  You need to
-  configure <application>mutt</application> so that it knows where to
+  by way of <application>procmail</application>.  All that's left to
+  do is to configure <application>mutt</application> so that it knows where to
   find your email messages so that you can view them.
 </para>
 
@@ -883,7 +884,7 @@ here and wants mds "/usr/bin/procmail"&#39; &#62;&#62; ~&#47;.fetchmailrc
   <application>procmail</application>&#41;, while <varname>mbox</varname>
   defines where mail that you have read and responded to will be
   stored. All other settings are self-explanatory, and all have been
-  drawn directly from the muttrc man page.
+  drawn directly from the muttrc man page; refer to it for more options.
 </para>
 
 <note>
@@ -897,8 +898,13 @@ here and wants mds "/usr/bin/procmail"&#39; &#62;&#62; ~&#47;.fetchmailrc
 <screen>
   <prompt>darkstar:~&#36; </prompt> formail -ds &lt; ~&#47;Mail&#47;Inbox &#62;&#62; ~&#47;Mail&#47;Muttbox
   </screen>
-</note>
 
+  <para>
+    Rather than performing this conversion every time you check your
+    email, you might want to script it to happen automatically after
+    procmail is finished its job.
+  </para>
+</note>
 
 <para>
   The commands used to navigate around in <application>mutt</application> are highly