Index: pst/scanning/sane.xml
===================================================================
--- pst/scanning/sane.xml	(revision 03d517889b41308a138691b2191e3ec59fb4d83b)
+++ pst/scanning/sane.xml	(revision 345857adb35c65dea0e3f02042afc8f935bfb68a)
@@ -27,4 +27,6 @@
 <?dbhtml filename="sane.html"?>
 <title>SANE-&sane-version;</title>
+<indexterm zone="sane">
+<primary sortas="a-SANE">SANE</primary></indexterm>
 
 <sect2>
@@ -95,7 +97,10 @@
 <application><acronym>SANE</acronym></application></title>
 
-<sect3><title>Preparing your system for scanner access</title>
+<sect3 id="sane-kernel"><title>Preparing your system for scanner access</title>
+<indexterm zone="sane sane-kernel">
+<primary sortas="d-Scanning-devices">Scanning devices</primary></indexterm>
+
 <para>To access your scanner, you will probably need the related kernel
-drivers or additional support packages (<application>libusb</application>). 
+drivers or additional support packages (<xref linkend="libusb"/>). 
 A <acronym>SCSI</acronym> scanner will need <acronym>SCSI</acronym> 
 drivers, a parallel port scanner needs parallel port support (you should use 
@@ -103,5 +108,5 @@
 will need the <application>libusb</application> package and a 
 <acronym>SCSI</acronym> system for emulation. Be sure that you have got the 
-necessary drivers to access the devices.</para>
+necessary drivers configured to access the devices.</para>
 </sect3>
 
@@ -113,6 +118,9 @@
 
 <screen><userinput><command>./configure --prefix=/usr --sysconfdir=/etc &amp;&amp;
-make &amp;&amp;
-make install</command></userinput></screen>
+make</command></userinput></screen>
+
+<para>Now, as the root user:</para>
+
+<screen><userinput role='root'><command>make install</command></userinput></screen>
 </sect3>
 
@@ -132,12 +140,15 @@
 
 <screen><userinput><command>./configure --prefix=/usr &amp;&amp;
-make &amp;&amp;
-make install</command></userinput></screen>
+make</command></userinput></screen>
+
+<para>Now, as the root user:</para>
+
+<screen><userinput role='root'><command>make install</command></userinput></screen>
 
 <para>If <application>GIMP</application> was linked into the build and you 
 wish <application>GIMP</application> to use <command>xscanimage</command> as 
-a scanning plugin, issue the following command:</para>
-
-<screen><userinput><command>ln -s /usr/bin/xscanimage /usr/lib/gimp/2.0/plug-ins</command></userinput></screen>
+a scanning plugin, issue the following command as the root user:</para>
+
+<screen><userinput role='root'><command>ln -s /usr/bin/xscanimage /usr/lib/gimp/2.0/plug-ins</command></userinput></screen>
 </sect3>
 
@@ -156,6 +167,8 @@
 <title>Configuring <application><acronym>SANE</acronym></application></title>
 
-<sect3><title>Config files</title>
+<sect3 id="sane-config"><title>Config files</title>
 <para><filename>/etc/sane.d/*.conf</filename></para>
+<indexterm zone="sane sane-config">
+<primary sortas="e-etc-sane.d-conf">/etc/sane.d/*.conf</primary></indexterm>
 </sect3>
 
@@ -182,12 +195,12 @@
 <sect4><title>Configuration and setup of the <command>saned</command> 
 daemon</title>
-<para>The <command>saned</command> daemon is not meant to be used for untrusted 
-clients. You should provide <application>tcpwrapper</application> and/or 
-firewall protection to insure only trusted clients access the daemon. Due to 
-the complex security requirements to insure only trusted clients access the 
-daemon, <acronym>BLFS</acronym> does not provide instructions to configure the 
-<command>saned</command> daemon. If you desire to make the daemon available, 
-ensure you provide adequate security, configure your 
-<filename>[x]inetd.conf</filename> file and send a 
+<para>The <command>saned</command> daemon is not meant to be used for 
+untrusted clients. You should provide <xref linkend="tcpwrappers"/> and/or 
+<xref linkend="fw-firewall"/> protection to insure only trusted clients access 
+the daemon. Due to the complex security requirements to insure only trusted 
+clients access the daemon, <acronym>BLFS</acronym> does not provide 
+instructions to configure the <command>saned</command> daemon. If you desire 
+to make the daemon available, ensure you provide adequate security, configure 
+your <filename>[x]inetd.conf</filename> file and send a 
 <userinput>SIGHUP</userinput> to the [x]inetd daemon. Some good information for 
 setting up and securing the <command>saned</command> daemon can be found at 
@@ -201,71 +214,133 @@
 <title>Contents</title>
 
-<sect3><title>Back ends:</title>
-<para>The <application><acronym>SANE</acronym></application>-backends package 
-contains 
-<command>gamma4scanimage</command>, 
-<command>sane-config</command>, 
-<command>saned</command>, 
-<command>sane-find-scanner</command>, 
-<command>scanimage</command>, 
-the <filename class='libraryfile'>libsane</filename> library and 
-numerous scanner backend modules. See 
+<bridgehead renderas="sect4">Back Ends:</bridgehead>
+<segmentedlist>
+<segtitle>Installed Programs</segtitle>
+<segtitle>Installed Libraries</segtitle>
+<segtitle>Installed Directories</segtitle>
+
+<seglistitem>
+<seg>gamma4scanimage, sane-config, saned, sane-find-scanner and scanimage</seg>
+<seg>libsane.so and numerous scanner backend modules</seg>
+<seg>/etc/sane.d, /usr/include/sane, /usr/lib/sane, /usr/share/sane and 
+/usr/share/doc/sane-&sane-version;</seg>
+</seglistitem>
+</segmentedlist>
+
+<bridgehead renderas="sect4">Front Ends:</bridgehead>
+<segmentedlist>
+<segtitle>Installed Programs</segtitle>
+<segtitle>Installed Library</segtitle>
+<segtitle>Installed Directory</segtitle>
+
+<seglistitem>
+<seg>scanadf, xcam and xscanimage</seg>
+<seg><application>GIMP</application> plugin imbedded in 
+<command>xscanimage</command></seg>
+<seg>/usr/share/sane</seg>
+</seglistitem>
+</segmentedlist>
+
+<variablelist>
+<bridgehead renderas="sect3">Short Descriptions</bridgehead>
+<?dbfo list-presentation="list"?>
+
+<varlistentry id="gamma4scanimage">
+<term><command>gamma4scanimage</command></term>
+<listitem><para>creates a gamma table in the format expected by 
+<command>scanimage</command>.</para>
+<indexterm zone="sane gamma4scanimage">
+<primary sortas="b-gamma4scanimage">gamma4scanimage</primary>
+</indexterm></listitem>
+</varlistentry>
+
+<varlistentry id="sane-config-prog">
+<term><command>sane-config</command></term>
+<listitem><para>is a tool used to determine the compiler and linker flags that 
+should be used to compile and link 
+<application><acronym>SANE</acronym></application>.</para>
+<indexterm zone="sane sane-config-prog">
+<primary sortas="b-sane-config">sane-config</primary>
+</indexterm></listitem>
+</varlistentry>
+
+<varlistentry id="saned">
+<term><command>saned</command></term>
+<listitem><para>is the <application><acronym>SANE</acronym></application> 
+daemon that allows remote clients to access image acquisition devices 
+available on the local host.</para>
+<indexterm zone="sane saned">
+<primary sortas="b-saned">saned</primary>
+</indexterm></listitem>
+</varlistentry>
+
+<varlistentry id="sane-find-scanner">
+<term><command>sane-find-scanner</command></term>
+<listitem><para>is a command-line tool to find <acronym>SCSI</acronym> and 
+<acronym>USB</acronym> scanners and determine their device files. Its primary 
+aim is to make sure that scanners can be detected by 
+<application><acronym>SANE</acronym></application> backends.</para>
+<indexterm zone="sane sane-find-scanner">
+<primary sortas="b-sane-find-scanner">sane-find-scanner</primary>
+</indexterm></listitem>
+</varlistentry>
+
+<varlistentry id="scanadf">
+<term><command>scanadf</command></term>
+<listitem><para>is a command-line interface to control image acquisition 
+devices which are equipped with an automatic document feeder
+(<acronym>ADF</acronym>).</para>
+<indexterm zone="sane scanadf">
+<primary sortas="b-scanadf">scanadf</primary>
+</indexterm></listitem>
+</varlistentry>
+
+<varlistentry id="scanimage">
+<term><command>scanimage</command></term>
+<listitem><para>is a command line interface for scanning from image 
+acquisition devices such as flatbed scanners or cameras. It is also used to 
+list the available backend devices.</para>
+<indexterm zone="sane scanimage">
+<primary sortas="b-scanimage">scanimage</primary>
+</indexterm></listitem>
+</varlistentry>
+
+<varlistentry id="xcam">
+<term><command>xcam</command></term>
+<listitem><para>is a graphical camera front end for 
+<application><acronym>SANE</acronym></application>.</para>
+<indexterm zone="sane xcam">
+<primary sortas="b-xcam">xcam</primary>
+</indexterm></listitem>
+</varlistentry>
+
+<varlistentry id="xscanimage">
+<term><command>xscanimage</command></term>
+<listitem><para>is a graphical user interface for scanning.</para>
+<indexterm zone="sane xscanimage">
+<primary sortas="b-xscanimage">xscanimage</primary>
+</indexterm></listitem>
+</varlistentry>
+
+<varlistentry id="libsane">
+<term><filename class='libraryfile'>libsane.so</filename></term>
+<listitem><para>is the application programming interface that is used to 
+communicate between frontends and backends.</para>
+<indexterm zone="sane libsane">
+<primary sortas="c-libsane">libsane.so</primary>
+</indexterm></listitem>
+</varlistentry>
+
+<varlistentry id="libsane-module">
+<term><filename class='libraryfile'>libsane-*.so</filename></term>
+<listitem><para>modules are backend scanning library plugins used to interface 
+with scanning devices. See 
 <ulink url="http://www.sane-project.org/sane-supported-devices.html"/> 
 for a list of supported backends.</para>
-</sect3>
-
-<sect3><title>Front ends:</title>
-<para>The <application><acronym>SANE</acronym></application>-frontends package 
-contains 
-<command>scanadf</command>, 
-<command>xcam</command>, 
-<command>xscanimage</command> and a <application>GIMP</application> plugin 
-imbedded in <command>xscanimage</command>.</para>
-</sect3>
-
-</sect2>
-
-<sect2>
-<title>Description</title>
-
-<sect3><title>gamma4scanimage</title>
-<para><command>gamma4scanimage</command> creates a gamma table in the format 
-expected by <command>scanimage</command>.</para></sect3>
-
-<sect3><title>sane-config</title>
-<para><command>sane-config</command> is a tool used to determine the compiler 
-and linker flags that should be used to compile and link 
-<application><acronym>SANE</acronym></application>.</para></sect3>
-
-<sect3><title>saned</title>
-<para><command>saned</command> is the 
-<application><acronym>SANE</acronym></application> daemon that allows remote 
-clients to access image acquisition devices available on the local 
-host.</para></sect3>
-
-<sect3><title>sane-find-scanner</title>
-<para><command>sane-find-scanner</command> is a command-line tool to find 
-<acronym>SCSI</acronym> and <acronym>USB</acronym> scanners and determine 
-their device files. Its primary aim is to make sure that scanners can be 
-detected by <application><acronym>SANE</acronym></application> 
-backends.</para></sect3>
-
-<sect3><title>scanadf</title>
-<para><command>scanadf</command> is a command-line interface to control image 
-acquisition devices which are equipped with an automatic document feeder 
-(<acronym>ADF</acronym>).</para></sect3>
-
-<sect3><title>scanimage</title>
-<para><command>scanimage</command> is a command line interface for scanning 
-from image acquisition devices such as flatbed scanners or cameras. It is 
-also used to list the available backend devices.</para></sect3>
-
-<sect3><title>xcam</title>
-<para><command>xcam</command> is a graphical camera front end for 
-<application><acronym>SANE</acronym></application>.</para></sect3>
-
-<sect3><title>xscanimage</title>
-<para><command>xscanimage</command> is a graphical user interface for 
-scanning.</para></sect3>
+<indexterm zone="sane libsane-module">
+<primary sortas="c-libsane-module">libsane-*.so</primary>
+</indexterm></listitem>
+</varlistentry>
+</variablelist>
 
 </sect2>
