From b32e9c2737061a7f362eba000c91e41e8edf3a65 Mon Sep 17 00:00:00 2001
From: gferg <>
Date: Mon, 7 Jan 2002 15:24:19 +0000
Subject: [PATCH] updated

---
 LDP/guide/docbook/abs-guide/Change.log     |  82 +++
 LDP/guide/docbook/abs-guide/abs-guide.sgml | 684 ++++++++++++++++++---
 LDP/guide/docbook/abs-guide/ex56.sh        |   2 +-
 LDP/guide/docbook/abs-guide/ex62.sh        |  15 +-
 LDP/guide/docbook/abs-guide/ex9.sh         |  10 +-
 LDP/guide/docbook/abs-guide/symlinks.sh    |   4 +-
 LDP/guide/docbook/abs-guide/symlinks2.sh   |   6 +-
 LDP/guide/docbook/abs-guide/weirdvars.sh   |   6 +-
 8 files changed, 726 insertions(+), 83 deletions(-)

diff --git a/LDP/guide/docbook/abs-guide/Change.log b/LDP/guide/docbook/abs-guide/Change.log
index 9c542d80..343dee01 100644
--- a/LDP/guide/docbook/abs-guide/Change.log
+++ b/LDP/guide/docbook/abs-guide/Change.log
@@ -2,6 +2,88 @@ RELEASE HISTORY
 ------- -------
 Change log
 
+Version 1.0.X interim release
+
+1) Fix up comments in "weirdvars.sh" example.
+
+2) In "Variables" chapter, slight wording change in first paragraph.
+
+3) Slight changes to "ex9.sh" example.
+
+4) Added redirection as an alternative remedy to the script hang problem with
+   background commands in "Job Control Commands" section of "Internal
+   Commands" chapter.
+
+5) In "Text Processing Commands" section of "External Commands" chapter:
+      Added "-q" option at "grep", with in-line example.
+      Added usage example for "cut".
+      Much more information on "uniq -c", and added "wf.sh" example.
+
+6) In "Functions" chapter:
+     Added more info on oversize (> 256) return values.   
+     Modified "ex62.sh" example.
+     Reorganized "Local Variables" section.
+     Added note that before function call, all variables within functions
+     are local, not just those explicitly declared as such.
+
+7) Add section on "Shell Scripting Under Windows" to "Miscellany" chapter.
+
+8) In "String Manipulation" section of "Variables Revisited" chapter:
+      Bugfix in comment in "%%" substring removal example.
+      Added "cvt.sh" example at "%%" substring removal discussion.
+      Added subsection on using "awk" functionality for string manipulation,
+      with added "substring-extraction.sh" example.
+
+9) In "$RANDOM" section of "Variables Revisited" chapter:
+      Removed superfluous "note" icon at beginning of section.
+      Added example of using "awk" rand() function to generate random numbers.
+
+10) In "Command Substitution" chapter:
+      Added discussion and example of extending Bash toolset.
+      Added footnote about what exactly constitutes a "command".
+
+11) In "System and Administrative Commands" chapter:
+    Added "lastlog" command.   
+    More info on "route" and "netstat".
+    Fixed reference to "crond" at "logrotate".
+    Added "tmpwatch".
+    Added "sar".
+
+12) In "Miscellaneous Commands" section of "External Commands" chapter,
+    added more info and an example to "dd".
+
+13) In "Math Commands" section of "External Commands" chapter:
+    Added an alternative method of invoking 'bc', with "alt-bc.sh" example.
+    Added using "awk" math commands, with "hypotenuse.sh" example.
+
+14) In "Archiving Commands" section of "External Commands" chapter,
+    added footnote to "tar".
+
+15) In "Bibliography" section:
+      Cleaned up cross reference to University of Alberta site.
+      Added comp.unix.shell newsgroup reference.
+
+16) Made corrections to "symlinks.sh" and "symlinks2.sh" examples,
+    per Dominik 'Aeneas' Schnitzer.
+
+17) In "Starting Off With a Sha-Bang" chapter, clarified footnote explaining
+   "magic numbers", per Stanislav Brabec's suggestion.
+
+18) In "I/O Redirection" chapter, added stdout redirection instance, with
+    example.
+
+19) In "Sed and Awk Micro-Primer" appendix:
+    Added $filename to in-line examples.
+    Fixup on "END" command block description.
+
+20) Added semicolons as necessary to terminate commands in Perl examples.    
+
+21) Added "History Commands" appendix. 
+
+
+
+
+
 Version 1.0 (stable!), released 10/14/01
 
 1) Quoted "$LOGFILE" in in-line example in "Scripting With Style" subsection
diff --git a/LDP/guide/docbook/abs-guide/abs-guide.sgml b/LDP/guide/docbook/abs-guide/abs-guide.sgml
index dd93ee19..13f79d8c 100644
--- a/LDP/guide/docbook/abs-guide/abs-guide.sgml
+++ b/LDP/guide/docbook/abs-guide/abs-guide.sgml
@@ -213,13 +213,19 @@ Uncomment line below to generate index.
 <!ENTITY idelete SYSTEM "idelete.sh">
 <!ENTITY matchstring SYSTEM "match-string.sh">
 <!ENTITY bashandperl SYSTEM "bashandperl.sh">
+<!ENTITY cvt SYSTEM "cvt.sh">
+<!ENTITY wf SYSTEM "wf.sh">
+<!ENTITY hypot SYSTEM "hypotenuse.sh">
+<!ENTITY random2 SYSTEM "random2.sh">
+<!ENTITY altbc SYSTEM "alt-bc.sh">
+<!ENTITY substringex SYSTEM "substring-extraction.sh">
 <!ENTITY bashrc SYSTEM "bashrc">
 ]>
 
 <book>
   <bookinfo>
     <title>Advanced Bash-Scripting Guide</title>
-    <subtitle>A complete guide to shell scripting, using Bash</subtitle>
+    <subtitle>A complete guide to shell scripting</subtitle>
 
 
     <author>
@@ -231,8 +237,8 @@ Uncomment line below to generate index.
       </affiliation>
     </author>
 
-
-    <pubdate>14 October 2001</pubdate>
+    <releaseinfo>1.1</releaseinfo>
+    <pubdate>06 January 2002</pubdate>
 
 
     <revhistory>
@@ -279,9 +285,15 @@ Uncomment line below to generate index.
         <revnumber>1.0</revnumber>
         <date>14 October 2001</date>
         <authorinitials>mc</authorinitials>
-        <revremark>Bugfixes, reorganization, material added. This book
-	  has finally reached the point where it can be designated a
-	  stable release.</revremark>
+        <revremark>Bugfixes, reorganization, material added.
+	  Stable release.</revremark>
+      </revision>
+
+      <revision>
+        <revnumber>1.1</revnumber>
+        <date>06 January 2002</date>
+        <authorinitials>mc</authorinitials>
+        <revremark>Bugfixes, material and scripts added.</revremark>
       </revision>
 
     </revhistory>
@@ -303,7 +315,7 @@ Uncomment line below to generate index.
       <para>The latest update of this document, as an archived
 	<quote>tarball</quote> including both the SGML
 	source and rendered HTML, may be downloaded from <ulink
-	url="http://personal.riverusers.com/~thegrendel/abs-guide-1.0.tar.gz">
+	url="http://personal.riverusers.com/~thegrendel/abs-guide-1.1.tar.gz">
 	the author's home site</ulink>.  See the <ulink
 	url="http://personal.riverusers.com/~thegrendel/Change.log">change
 	log</ulink> for a revision history.</para>
@@ -529,10 +541,10 @@ Uncomment line below to generate index.
       is a set of commands to be fed to the command interpreter indicated.
       <anchor id="magnumref">The <token>#!</token> is actually a two-byte
 
-        <footnote><para>Some flavors
-        of UNIX take a four-byte magic number,
-        requiring a blank after the <token>!</token>,
-        <userinput>#! /bin/sh</userinput>.</para></footnote>
+        <footnote><para>Some flavors of UNIX (those based on 4.2BSD)
+          take a four-byte magic number, requiring
+          a blank after the <token>!</token>,
+          <userinput>#! /bin/sh</userinput>.</para></footnote>
 
 	<indexterm>
 	  <primary>magic number</primary>
@@ -2215,7 +2227,7 @@ echo $a   # 28</programlisting></para>
         of quantities, string parsing, and are indispensable for working
         in the abstract with symbols - tokens that represent something
         else. A variable is nothing more than a location or set of
-        locations in computer memory that holds an item of data.</para>
+        locations in computer memory holding an item of data.</para>
 
      <sect1 id="varsubn">
         <title>Variable Substitution</title>
@@ -6048,12 +6060,18 @@ echo ${stringZ##a*C}     # abc
 #        |------------|
 
 echo ${stringZ%b*c}      # abcABC123ABCa
-# Strip out shortest match between 'a' and 'C', from back of $stringZ.
+# Strip out shortest match between 'b' and 'c', from back of $stringZ.
 
 echo ${stringZ%%b*c}     # a
-# Strip out longest match between 'a' and 'C', from back of $stringZ.</programlisting>
+# Strip out longest match between 'b' and 'c', from back of $stringZ.</programlisting>
 	  </para>  
 
+	    <example id="cvt">
+	      <title>Converting graphic file formats, with filename change</title>
+	      <programlisting>&cvt;</programlisting>
+	    </example>
+
+
 	  </listitem>
 	</varlistentry>
 
@@ -6148,8 +6166,27 @@ echo ${stringZ/%abc/XYZ}          # abcABC123ABCXYZ
 
       </variablelist>
 
-     <para>For further discussion of string manipulation in scripts,
-       refer to <xref linkend="Parameter-Substitution"> and the
+    <sect2 id="awkstringmanip">
+      <title>Manipulating strings using awk</title>
+
+          <para>A Bash script may invoke the string manipulation facilities of
+	    <link linkend="awkref">awk</link> as an alternative to using its
+	    built-in operations.</para>
+
+	    <example id="substringex">
+	      <title>Alternate ways of extracting substrings</title>
+	      <programlisting>&substringex;</programlisting>
+	    </example>
+
+    </sect2> <!-- Manipulating strings using awk -->
+
+
+
+    <sect2 id="strfdisc">
+      <title>Further Discussion</title>
+   
+     <para>For more on string manipulation in scripts, refer to <xref
+       linkend="Parameter-Substitution"> and the
        <link linkend="expextrsub">relevant section</link> of the <link
        linkend="exprref">expr</link> command listing. For script examples,
        see: <orderedlist>
@@ -6161,6 +6198,10 @@ echo ${stringZ/%abc/XYZ}          # abcABC123ABCXYZ
        </orderedlist>
       </para>	 
 
+    </sect2> <!-- Further Discussion -->
+    
+
+
     </sect1> <!-- Manipulating Strings -->
 
 
@@ -6698,10 +6739,10 @@ echo "number = $number"     # number = 0
 	  <secondary>$RANDOM</secondary>
 	</indexterm>
 	<title>$RANDOM: generate random integer</title>
-	<note><para>$RANDOM is an internal Bash function (not a constant) that
+	<para>$RANDOM is an internal Bash function (not a constant) that
 	  returns a <emphasis>pseudorandom</emphasis> integer in the range
 	  0 - 32767. $RANDOM should <replaceable>not</replaceable> be used
-	  to generate an encryption key.</para></note>
+	  to generate an encryption key.</para>
 
 	<example id="ex21">
 	  <title>Generating random numbers</title>
@@ -6731,7 +6772,8 @@ echo "number = $number"     # number = 0
 	</example>
 
 	<para><anchor id="urandomref"></para>
-	<note><para>The <filename>/dev/urandom</filename> device-file provides
+	<note>
+	<para>The <filename>/dev/urandom</filename> device-file provides
 	  a means of generating much more <quote>random</quote>
 	  pseudorandom numbers than the <varname>$RANDOM</varname>
 	  variable.  <userinput>dd if=/dev/urandom of=targetfile
@@ -6740,7 +6782,22 @@ echo "number = $number"     # number = 0
 	  to a variable in a script requires a workaround, such as
 	  filtering through <link linkend="odref">od</link> (as in
 	  above example) or using <link linkend="ddref">dd</link>
-	  (see <xref linkend="blotout">).</para></note>
+	  (see <xref linkend="blotout">).</para>
+
+        <para><anchor id="awkrandomref"></para>
+	  
+        <para>There are also other means of generating pseudorandom
+          numbers in a script. <command>Awk</command> provides a
+	  convenient means of doing this.</para>
+
+	    <example id="random2">
+	      <title>Pseudorandom numbers, using <link
+	        linkend="awkref">awk</link></title>
+	      <programlisting>&random2;</programlisting>
+	    </example>
+
+	  </note>
+
 
 
       </sect1> <!-- RANDOM: generate random integer -->
@@ -8582,9 +8639,10 @@ done
 	      <para><anchor id="waithang"></para>
               <tip>
 	      <para>Within a script, running a command in the background
-		with an ampersand (&amp;) may cause the script to hang
-		until <keycap>ENTER</keycap> is hit. This can be a
-		major annoyance.
+		with an ampersand (&amp;) may cause the script
+		to hang until <keycap>ENTER</keycap> is hit. This
+		seems to occur with commands that write to
+		<filename>stdout</filename>. It can be a major annoyance.
 		  <programlisting>#!/bin/bash
 # test.sh		  
 
@@ -8612,6 +8670,10 @@ wait</programlisting>
  [bozo@localhost test-scripts]$ total 1
  -rwxr-xr-x    1 bozo     bozo           34 Oct 11 15:09 test.sh</computeroutput>
                </screen>
+	        <link linkend="ioredirref">Redirecting</link> the
+                output of the command to a file or even to
+		<filename>/dev/null</filename> also takes care of this
+		problem.
               </para>
 	      </tip>
 
@@ -9982,7 +10044,68 @@ gzip -cd patchXX.gz | patch -p0
 # and finally writes the result to an output file.</programlisting></para>
  
              <para>The useful <option>-c</option> option prefixes each line of
-	       the input file with the number of occurrences.</para>
+	       the input file with its number of occurrences.</para>
+	     <para>
+	      <screen>
+<prompt>bash$ </prompt><userinput>cat testfile</userinput>
+<computeroutput>This line occurs only once.
+ This line occurs twice.
+ This line occurs twice.
+ This line occurs three times.
+ This line occurs three times.
+ This line occurs three times.</computeroutput>
+
+
+<prompt>bash$ </prompt><userinput>uniq -c testfile</userinput>
+<computeroutput>      1 This line occurs only once.
+       2 This line occurs twice.
+       3 This line occurs three times.</computeroutput>
+
+
+<prompt>bash$ </prompt><userinput>sort testfile | uniq -c | sort -nr</userinput>
+<computeroutput>      3 This line occurs three times.
+       2 This line occurs twice.
+       1 This line occurs only once.</computeroutput>
+	      </screen>
+	     </para>
+
+	     <para>The <userinput>sort INPUTFILE | uniq -c | sort -nr</userinput>
+	       command string produces a <emphasis>frequency
+	       of occurrence</emphasis> listing on the
+	       <filename>INPUTFILE</filename> file (the
+	       <option>-nr</option> options to <command>sort</command>
+	       cause a reverse numerical sort). This template finds
+	       use in analysis of log files and dictionary lists, and
+	       wherever the lexical structure of a document needs to
+	       be examined.</para>
+
+	    <example id="wf">
+	      <title>Word Frequency Analysis</title>
+	      <programlisting>&wf;</programlisting>
+	    </example>	    
+
+	     <para>
+	       <screen>
+<prompt>bash$ </prompt><userinput>cat testfile</userinput>
+<computeroutput>This line occurs only once.
+ This line occurs twice.
+ This line occurs twice.
+ This line occurs three times.
+ This line occurs three times.
+ This line occurs three times.</computeroutput>
+
+
+<prompt>bash$ </prompt><userinput>./wf.sh testfile</userinput>
+<computeroutput>      6 this
+       6 occurs
+       6 line
+       3 times
+       3 three
+       2 twice
+       1 only
+       1 once</computeroutput>
+	       </screen>
+	     </para>
 
 	  </listitem>
 	</varlistentry>
@@ -10045,6 +10168,16 @@ gzip -cd patchXX.gz | patch -p0
 	    <para>Using <command>cut</command> to list the OS and kernel version:
 	      <programlisting>uname -a | cut -d" " -f1,3,11,12</programlisting></para>
 
+	    <para>Using <command>cut</command> to extract message headers from
+	      an e-mail folder:
+
+	      <screen><prompt>bash$ </prompt><userinput>grep '^Subject:' read-messages | cut -c10-80</userinput>
+<computeroutput>Re: Linux suitable for mission-critical apps?
+ MAKE MILLIONS WORKING AT HOME!!!
+ Spam complaint
+ Re: Spam complaint</computeroutput></screen>
+	    </para>
+
 	    <para>Using <command>cut</command> to parse a file:
 	      <programlisting># List all the users in /etc/passwd.
 
@@ -10338,7 +10471,22 @@ printf 'a b\nc  d\n\n\n\n\n\000\n\000e\000\000\nf' | grep -c '$'    # 9
 	    <para>If there is a successful match, <command>grep</command>
 	      returns an <link linkend="exitstatusref">exit status</link>
 	      of 0, which makes it useful in a condition test in a
-	      script.</para>
+	      script, especially in combination with the <option>-q</option>
+	      option to suppress output.
+	        <programlisting>SUCCESS=0                      # if grep lookup succeeds
+word=Linux
+filename=data.file
+
+grep -q "$word" "$filename"    # The "-q" option causes nothing to echo to stdout.
+
+if [ $? -eq $SUCCESS ]
+then
+  echo "$word found in $filename"
+else
+  echo "$word not found in $filename"
+fi</programlisting>
+            </para>
+
 
 	    <para><xref linkend="online"> demonstrates how to use
 	      <command>grep</command> to search for a word pattern in
@@ -10901,8 +11049,20 @@ printf 'a b\nc  d\n\n\n\n\n\000\n\000e\000\000\nf' | grep -c '$'    # 9
 	      accept <link linkend="gzipref">gzip</link> compression
 	      options, such as <command>tar czvf archive-name.tar.gz
 	      *</command>, which recursively archives and compresses all
-	      files (except <link linkend="dotfilesref">dotfiles</link>)
-	      in a directory tree.</para>
+	      files in a directory tree except <link
+	      linkend="dotfilesref">dotfiles</link> in the current
+	      working directory (<command>$PWD</command>).
+		<footnote>
+		  <para>
+		    A <command>tar czvf ...</command>
+		    <emphasis>will</emphasis> include dotfiles in
+		    directories <emphasis>below</emphasis> the current
+		    working directory. This is an undocumented
+		    <command>tar</command> <quote>feature</quote>.
+		  </para>
+		</footnote>
+            </para>		
+		
 
 	    <para>Some useful <command>tar</command> options:  
 	      <orderedlist>
@@ -10974,8 +11134,10 @@ printf 'a b\nc  d\n\n\n\n\n\000\n\000e\000\000\nf' | grep -c '$'    # 9
 	    <secondary>cpio</secondary>
 	  </indexterm>
 	  <listitem>
-	    <para>This specialized archiving copy command is rarely seen any more,
-	      having been supplanted by
+	    <para>This specialized archiving copy command
+	      (<command>c</command>o<command>p</command>y
+	      <command>i</command>nput and <command>o</command>utput)
+	      is rarely seen any more, having been supplanted by
 	      <command>tar</command>/<command>gzip</command>. It still
 	      has its uses, such as moving a directory tree.</para>
 
@@ -12235,7 +12397,9 @@ printf 'a b\nc  d\n\n\n\n\n\000\n\000e\000\000\nf' | grep -c '$'    # 9
 	      the rescue.</para>
 
 	    <para>Here is a simple template for using
-	      <command>bc</command> to calculate a script variable.</para>
+	      <command>bc</command> to calculate a script
+	      variable. This uses <link linkend="commandsubref">command
+	      substitution</link>.</para>
 
 	      <para>
               <screen>
@@ -12253,6 +12417,63 @@ printf 'a b\nc  d\n\n\n\n\n\000\n\000e\000\000\nf' | grep -c '$'    # 9
               <programlisting>&base;</programlisting>
             </example>
 
+	      <para>An alternate method of invoking <command>bc</command>
+		involves using a <link linkend="heredocref">here
+		document</link> embedded within a <link
+		linkend="commandsubref">command substitution</link>
+		block. This is especially appropriate when a script
+		needs to pass a list of options and commands to
+		<command>bc</command>.</para>
+
+              <para>
+	      <programlisting>variable=`bc << LIMIT_STRING
+options
+statements
+operations
+LIMIT_STRING
+`
+
+...or...
+
+
+variable=$(bc << LIMIT_STRING
+options
+statements
+operations
+LIMIT_STRING
+)</programlisting>
+              </para>
+
+
+            <example id="altbc">
+              <title>Another way to invoke <command>bc</command></title>
+              <programlisting>&altbc;</programlisting>
+            </example>
+
+	  </listitem>
+	</varlistentry>
+
+
+	<varlistentry>
+	  <term><anchor id="awkmath"><command>awk</command></term>
+	  <indexterm>
+	    <primary>awk</primary>
+	  </indexterm>
+	  <indexterm>
+	    <primary>command</primary>
+	    <secondary>math</secondary>
+	  </indexterm>
+	  <listitem>
+	    <para>Yet another way of doing floating point math in
+	      a script is using <link linkend="awkref">awk's</link>
+	      built-in math functions in a <link linkend="shwrapper">shell
+	      wrapper</link>.</para>
+
+            <example id="hypot">
+              <title>Calculating the hypotenuse of a triangle</title>
+              <programlisting>&hypot;</programlisting>
+            </example>
+
 	  </listitem>
 	</varlistentry>
 
@@ -12616,8 +12837,20 @@ echo -n "hello world" | dd cbs=1 conv=unblock 2> /dev/null
 	    <para>The <command>dd</command> command can copy raw data
 	      and disk images to and from devices, such as floppies and
 	      tape drives (<xref linkend="copycd">). A common use is
-	      creating boot floppies.
-		<programlisting>dd if=kernel-image of=/dev/fd0H1440</programlisting>
+	      creating boot floppies.</para>
+             <para>
+		<userinput>dd if=kernel-image of=/dev/fd0H1440</userinput>
+             </para>
+
+             <para>Similarly, <command>dd</command> can copy the entire
+	       contents of a floppy, even one formatted with a
+	       <quote>foreign</quote> OS, to the hard drive as an
+	       image file.</para>
+             <para>
+		<userinput>dd if=/dev/fd0 of=/home/bozo/projects/floppy.img</userinput>
+             </para>
+
+             <para>
 	      Other applications of <command>dd</command> include
 	      initializing temporary swap files (<xref linkend="ex73">)
 	      and ramdisks (<xref linkend="ramdisk">). It can even do a
@@ -13380,13 +13613,47 @@ setserial /dev/$DEVICE irq 0 ; setserial /dev/$DEVICE irq $IRQ</programlisting><
 	    <secondary>last</secondary>
 	  </indexterm>
 	  <listitem>
-	    <para> Gives information about previous commands, as stored
+	    <para>Gives information about previous commands, as stored
 	      in the <filename>/var/account/pacct</filename> file. Command
 	      name and user name can be specified by options. This is
 	      one of the GNU accounting utilities.</para>
 	  </listitem>
 	</varlistentry>
 
+	<varlistentry>
+	  <term><command>lastlog</command></term>
+	  <indexterm>
+	    <primary>lastlog</primary>
+	  </indexterm>
+	  <indexterm>
+	    <primary>command</primary>
+	    <secondary>last</secondary>
+	  </indexterm>
+	  <listitem>
+	    <para>List the last login time of all system users. This
+	      references the <filename>/var/log/lastlog</filename>
+	      file.</para>
+	    <para>
+	      <screen><prompt>bash$ </prompt><userinput>lastlog</userinput>
+<computeroutput>root          tty1                      Fri Dec  7 18:43:21 -0700 2001
+ bin                                     **Never logged in**
+ daemon                                  **Never logged in**
+ ...
+ bozo          tty1                      Sat Dec  8 21:14:29 -0700 2001</computeroutput>
+
+
+
+<prompt>bash$ </prompt><userinput>lastlog | grep root</userinput>
+<computeroutput>root          tty1                      Fri Dec  7 18:43:21 -0700 2001</computeroutput>
+	      </screen>
+	      </para>
+
+	      <caution><para>This command will fail if the user invoking
+		it does not have read permission for the
+		<filename>/var/log/lastlog</filename> file.</para></caution>
+	  </listitem>
+	</varlistentry>
+
 	<varlistentry>
 	  <term><command>lsof</command></term>
 	  <indexterm>
@@ -13641,11 +13908,13 @@ setserial /dev/$DEVICE irq 0 ; setserial /dev/$DEVICE irq $IRQ</programlisting><
 	    <secondary>netstat</secondary>
 	  </indexterm>
 	  <listitem>
-	    <para>Show current network information and statistics,
+	    <para>Show current network statistics and information, 
 	      such as routing tables and active connections. This utility
 	      accesses information in <filename>/proc/net</filename>
 	      (<xref linkend="devproc">). See <xref
 	      linkend="constat">.</para>
+	    <para><command>netstat -r</command> is equivalent to <link
+	      linkend="routeref">route</link>.</para>
 	  </listitem>
 	</varlistentry>
 
@@ -13742,6 +14011,42 @@ setserial /dev/$DEVICE irq 0 ; setserial /dev/$DEVICE irq $IRQ</programlisting><
 	  </listitem>
 	</varlistentry>
 
+	<varlistentry>
+	  <term><command>sar</command></term>
+	  <indexterm>
+	    <primary>sar</primary>
+	  </indexterm>
+	  <indexterm>
+	    <primary>command</primary>
+	    <secondary>system activity report</secondary>
+	  </indexterm>
+	  <listitem>
+	    <para>Invoking <command>sar</command> (system activity report)
+	      gives a very detailed rundown on system statistics.
+	      This command is found on some commercial UNIX
+	      systems, but is not part of the base Linux
+	      distribution.  It is contained in the <ulink
+	      url="http://perso.wanadoo.fr/sebastien.godard/">
+	      sysstat utilities</ulink> package, written by <ulink
+	      url="mailto:sebastien.godard@wanadoo.fr">Sebastien
+	      Godard</ulink>.</para>
+
+	    <screen>
+<prompt>bash$ </prompt><userinput>sar</userinput>
+<computeroutput>Linux 2.4.7-10 (localhost.localdomain) 	12/31/2001
+
+ 10:30:01 AM       CPU     %user     %nice   %system     %idle
+ 10:40:00 AM       all      1.39      0.00      0.77     97.84
+ 10:50:00 AM       all     76.83      0.00      1.45     21.72
+ 11:00:00 AM       all      1.32      0.00      0.69     97.99
+ 11:10:00 AM       all      1.17      0.00      0.30     98.53
+ 11:20:00 AM       all      0.51      0.00      0.30     99.19
+ 06:30:00 PM       all    100.00      0.00    100.01      0.00
+ Average:          all      1.39      0.00      0.66     97.95</computeroutput>
+           </screen>
+	  </listitem>
+	</varlistentry>
+
       </variablelist>
 
       <variablelist id="syslog">
@@ -13792,7 +14097,7 @@ setserial /dev/$DEVICE irq 0 ; setserial /dev/$DEVICE irq $IRQ</programlisting><
 
 	    <para>This utility manages the system log files, rotating,
 	      compressing, deleting, and/or mailing them, as appropriate.
-	      Usually <command>cron</command> runs
+	      Usually <link linkend="cronref">crond</link> runs
 	      <command>logrotate</command> on a daily basis.</para>
 
 	     <para>Adding an appropriate entry to
@@ -14140,7 +14445,7 @@ echo `/sbin/ifconfig | grep ^[a-z] | awk '{print $1}'`
 	</varlistentry>
 
 	<varlistentry>
-	  <term><command>route</command></term>
+	  <term><anchor id="routeref"><command>route</command></term>
 	  <indexterm>
 	    <primary>route</primary>
 	  </indexterm>
@@ -14154,8 +14459,10 @@ echo `/sbin/ifconfig | grep ^[a-z] | awk '{print $1}'`
 
 	  <para>
 	      <screen><prompt>bash$ </prompt><userinput>route</userinput>
-<computeroutput>Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
- 127.0.0.0       *               255.0.0.0       U     0      0        0 lo</computeroutput>
+<computeroutput>Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
+ pm3-67.bozosisp *               255.255.255.255 UH       40 0          0 ppp0
+ 127.0.0.0       *               255.0.0.0       U        40 0          0 lo
+ default         pm3-67.bozosisp 0.0.0.0         UG       40 0          0 ppp0</computeroutput>
 	      </screen>
 	    </para>
 
@@ -14716,6 +15023,23 @@ then
 	  </listitem>
 	</varlistentry>
 
+	<varlistentry>
+	  <term><command>tmpwatch</command></term>
+	  <indexterm>
+	    <primary>tmpwatch</primary>
+	  </indexterm>
+	  <indexterm>
+	    <primary>command</primary>
+	    <secondary>tmpwatch</secondary>
+	  </indexterm>
+	  <listitem>
+	    <para>Automatically deletes files which have not been accessed
+	      within a specified period of time. Usually invoked by
+	      <link linkend="cronref">crond</link> to remove stale log
+	      files.</para>
+	  </listitem>
+	</varlistentry>
+
 	<varlistentry>
 	  <term><command>MAKEDEV</command></term>
 	  <indexterm>
@@ -15112,6 +15436,11 @@ print "even when I don't know where to find Perl.\n";
 
 	   <para><emphasis><anchor id="commandsubref">Command
 	     substitution</emphasis> reassigns the output of a command
+		<footnote><para>For purposes of <emphasis>command
+		substitution</emphasis>, a <command>command</command> may
+		be an external system command, an internal scripting
+		<emphasis>builtin</emphasis>, or even a script
+		function.</para></footnote>
 	     or even multiple commands; it literally plugs the command
 	     output into another context.</para>
 
@@ -15242,7 +15571,39 @@ variable2=`cat file2`   # Set "variable2" to contents of "file2".
              </para>
 	     </tip>
 
+	      <sidebar>
+              <para>Command substitution makes it possible to extend the
+		toolset available to Bash. It is simply a matter
+		of writing a program or script that outputs to
+		<filename>stdout</filename> (like a well-behaved UNIX
+		tool should) and assigning that output to a variable.</para>
 
+		<para>
+		<programlisting>#include &lt;stdio.h&gt;
+
+/*  "Hello, world." C program  */		
+
+int main()
+{
+  printf( "Hello, world." );
+  return (0);
+}</programlisting>
+	      <screen><prompt>bash$ </prompt><userinput>gcc -o hello hello.c</userinput>
+	      </screen>
+		</para>
+
+		<para>
+                <programlisting>#!/bin/bash
+# hello.sh		
+
+greeting=`./hello`
+echo $greeting</programlisting>
+	      <screen><prompt>bash$ </prompt><userinput>sh hello.sh</userinput>
+<computeroutput>Hello, world.</computeroutput>
+	        </screen>
+	        </para>
+	        </sidebar>
+	      
 	      <note><para>The <command>$(COMMAND)</command> form has
 		superseded backticks for command substitution.
 	      <programlisting>output=$(sed -n /"$1"/p $file)
@@ -15267,6 +15628,7 @@ variable2=`cat file2`   # Set "variable2" to contents of "file2".
 	 <listitem><para><xref linkend="pidid"></para></listitem>
 	 <listitem><para><xref linkend="monthlypmt"></para></listitem>
 	 <listitem><para><xref linkend="base"></para></listitem>
+	 <listitem><para><xref linkend="altbc"></para></listitem>
        </orderedlist>
      </para>  
 
@@ -15402,12 +15764,49 @@ let "z += 3"  #If quotes, then spaces and special operators allowed.
 
    : > filename
       # The > truncates file "filename" to zero length.
+      # If file not present, creates zero-length file (same effect as 'touch').
       # The : serves as a dummy placeholder, producing no output.
 
    >>
       # Redirect stdout to a file.
       # Creates the file if not present, otherwise appends to it.
 
+
+      # Single-line redirection commands (affect only the line they are on):
+      # --------------------------------------------------------------------
+   1>filename
+      # Redirect stdout to file "filename".
+   1>>filename
+      # Redirect and append stdout to file "filename".
+   2>filename
+      # Redirect stderr to file "filename".
+   2>>filename
+      # Redirect and append stderr to file "filename".
+
+      #==============================================================================
+      # Redirecting stdout, one line at a time.
+      LOGFILE=script.log
+
+      echo "This statement is sent to the log file, \"$LOGFILE\"." 1>$LOGFILE
+      echo "This statement is appended to \"$LOGFILE\"." 1>>$LOGFILE
+      echo "This statement is also appended to \"$LOGFILE\"." 1>>$LOGFILE
+      echo "This statement is echoed to stdout, and will not appear in \"$LOGFILE\"."
+      # These redirection commands automatically "reset" after each line.
+
+
+
+      # Redirecting stderr, one line at a time.
+      ERRORFILE=script.errors
+
+      bad_command1 2>$ERRORFILE       #  Error message sent to $ERRORFILE.
+      bad_command2 2>>$ERRORFILE      #  Error message appended to $ERRORFILE.
+      bad_command3                    #  Error message echoed to stderr,
+                                      #+ and does not appear in $ERRORFILE.
+      # These redirection commands also automatically "reset" after each line.
+      #==============================================================================
+
+
+
    2>&amp;1
       # Redirects stderr to stdout.
       # Error messages get sent to same place as standard output.
@@ -15753,8 +16152,8 @@ exit 0</programlisting>
 	  </para>
 	  </note>
 
-	<caution><para>Some utilities will not work in a here
-	  document.</para></caution>
+	<caution><para>Some utilities will not work inside a
+	  <emphasis>here document</emphasis>.</para></caution>
 
 	<para>For those tasks too complex for a <quote>here
 	  document</quote>, consider using the <command>expect</command>
@@ -17098,6 +17497,32 @@ fi
 	      value. This also permits returning large positive integer,
 	      using a bit of trickery.</para>
 
+	    <para>An alternate method of accomplishing this is to simply
+	      assign the <quote>return value</quote> to a global variable.
+	        <programlisting>Return_Val=   # Global variable to hold oversize return value of function.
+
+alt_return_test ()
+{
+  fvar=$1
+  Return_Val=$fvar
+  return   # Returns 0 (success).
+}
+
+alt_return_test 1
+echo $?                              # 0
+echo "return value = $Return_Val"    # 1
+
+alt_return_test 256
+echo "return value = $Return_Val"    # 256
+
+alt_return_test 257
+echo "return value = $Return_Val"    # 257
+
+alt_return_test 25701
+echo "return value = $Return_Val"    #25701</programlisting>
+            </para>
+
+
 	    <example id="max2">
 	      <title>Comparing two large integers</title>
 	      <programlisting>&max2;</programlisting>
@@ -17186,11 +17611,10 @@ Function ()  # This doesn't work.
 
 
       <sect1 id="localvar">
-        <title>Local Variables and Recursion</title>
+        <title>Local Variables</title>
 
       <variablelist id="localref">
-        <title><anchor id="localref1">Local variables make recursion
-	  possible.</title>
+        <title><anchor id="localref1">What makes a variable <quote>local</quote>?</title>
 
 	<varlistentry>
 	  <term>local variables</term>
@@ -17211,6 +17635,37 @@ Function ()  # This doesn't work.
 	      <programlisting>&ex62;</programlisting>
 	    </example>
 
+	    <caution>
+	    <para>Before a function is called, <emphasis>all</emphasis>
+	      variables declared within the function are invisible outside
+	      the body of the function, not just those explicitly declared
+	      as <emphasis>local</emphasis>.
+	        <programlisting>#!/bin/bash
+
+func ()
+{
+global_var=37    #  Visible only within the function block
+                 #+ before the function has been called. 
+}                # END OF FUNCTION
+
+echo "global_var = $global_var"  # global_var =
+                                 #  Function "func" has not yet been called,
+                                 #+ so $global_var is not visible here.
+
+func
+echo "global_var = $global_var"  # global_var = 37
+                                 # Has been set by function call.</programlisting>
+            </para>
+	    </caution>
+
+	  </listitem>
+	</varlistentry>
+
+      </variablelist>
+
+      <sect2 id="locvarrecur">
+        <title>Local variables make recursion possible.</title>
+
 	    <para>Local variables permit recursion,
 
 	      <footnote>
@@ -17259,12 +17714,9 @@ exit 0  # This script will not exit normally.</programlisting>
 	      resource-intensive and executes slowly, and is therefore
 	      generally not appropriate to use in a script.</para>
 
-	  </listitem>
-	</varlistentry>
+      </sect2>
 
-      </variablelist>
-
-      </sect1> <!-- Local Variables and Recursion -->
+      </sect1> <!-- Local Variables -->
 
   </chapter> <!-- Functions -->
 
@@ -18869,6 +19321,8 @@ fi</programlisting>
     <sect1 id="wrapper">
       <title>Shell Wrappers</title>
 
+      <para><anchor id="shwrapper"></para>
+
       <para>A <quote>wrapper</quote> is a shell script that embeds
 	a system command or utility, that saves a set of parameters
 	passed to to that command. Wrapping a script around a complex
@@ -19324,6 +19778,21 @@ exit 0</programlisting>
 
       </sect1> <!-- Portability Issues -->
 
+
+      <sect1 id="winscript">
+        <title>Shell Scripting Under Windows</title>
+
+	<para>Even users running <emphasis>that other</emphasis> OS can
+	  run UNIX-like shell scripts, and therefore benefit
+	  from many of the lessons of this book. The <ulink
+	  url="http://sourceware.cygnus.com/cygwin/">
+	  Cygwin</ulink> package from Cygnus and the <ulink
+	  url="http://www.mkssoftware.com/">MKS utilities</ulink> from
+	  Mortice Kern Associates add shell scripting capabilities to
+	  Windows.</para>
+
+      </sect1> <!-- Shell Scripting Under Windows -->
+
   </chapter> <!-- Miscellany -->
 
 
@@ -19896,7 +20365,7 @@ exit 0</programlisting>
     <biblioentry>
       <abstract>
 	<para>The O'Reilly books on Perl. (Actually, any O'Reilly books.)</para>
-	<para>-----------------------------------------------------------------------</para>
+	<para>---</para>
       </abstract>
     </biblioentry>
 
@@ -20025,8 +20494,8 @@ exit 0</programlisting>
 
     <biblioentry>
       <abstract>
-	<para>There is some nice material on I/O redirection (<xref
-	linkend="io-redirection">) in <ulink
+	<para>There is some nice material on <link
+	linkend="ioredirref">I/O redirection</link> in <ulink
 	url="http://sunsite.ualberta.ca/Documentation/Gnu/textutils-2.0/html_chapter/textutils_10.html">
 	chapter 10 of the textutils documentation</ulink> at the <ulink
 	url="http://sunsite.ualberta.ca/Documentation"> University of
@@ -20040,7 +20509,7 @@ exit 0</programlisting>
 	  Hohensee</ulink> has written the <ulink
 	  url="ftp://ftp.gwdg.de/pub/linux/install/clienux/interim/osimpa.tgz">
 	  osimpa</ulink> i386 assembler entirely as Bash scripts.</para>
-	<para>-------------------------------------------------------------------------</para>
+	<para>---</para>
       </abstract>
     </biblioentry>
 
@@ -20052,6 +20521,14 @@ exit 0</programlisting>
       </abstract>
     </biblioentry>
 
+    <biblioentry>
+      <abstract>
+        <para>The <ulink
+          url="news:comp.unix.shell">comp.os.unix.shell</ulink>
+          newsgroup.</para>
+      </abstract>
+    </biblioentry>
+
     <biblioentry>
       <abstract>
 	<para>The manpages for <command>bash</command> and
@@ -20318,12 +20795,14 @@ exit 0</programlisting>
       <para>From the command line and in a shell script, a sed operation may
        require quoting and certain options.</para>
 
-       <para><programlisting>sed -e '/^$/d'
-# The -e option causes the next string to be interpreted as an editing instruction.       
-# (If passing only a single instruction to "sed", the "-e" is optional.)
-# The "strong" quotes ('') protect the RE characters in the instruction
-# from reinterpretation as special characters by the body of the script.
+       <para><programlisting>sed -e '/^$/d' $filename
+# The -e option causes the next string to be interpreted as an editing instruction.
+#  (If passing only a single instruction to "sed", the "-e" is optional.)
+#  The "strong" quotes ('') protect the RE characters in the instruction
+#+ from reinterpretation as special characters by the body of the script.
 # (This reserves RE expansion of the instruction for sed.)
+#
+# Operates on the text contained in file $filename.
 </programlisting></para>
 
        <note><para>Sed uses the <option>-e</option> option
@@ -20331,7 +20810,7 @@ exit 0</programlisting>
 	 of instructions. If there is only a single instruction contained
 	 in the string, then this option may be omitted.</para></note>
 
-       <para><programlisting>sed -n '/xzy/p'
+       <para><programlisting>sed -n '/xzy/p' $filename
 # The -n option tells sed to print only those lines matching the pattern.
 # Otherwise all input lines would print.
 # The -e option not necessary here since there is only a single editing instruction.
@@ -20422,6 +20901,7 @@ exit 0</programlisting>
 	 <listitem><para><xref linkend="base"></para></listitem>
 	 <listitem><para><xref linkend="mailformat"></para></listitem>
 	 <listitem><para><xref linkend="rnd"></para></listitem>
+	 <listitem><para><xref linkend="wf"></para></listitem>
        </orderedlist>
      </para>  
 
@@ -20455,11 +20935,11 @@ exit 0</programlisting>
      <para>Strong quoting (single quotes) and curly brackets enclose
        segments of awk code within a shell script.</para>
 
-     <para><programlisting>awk '{print $3}'
-# Prints field #3 to stdout.
+     <para><programlisting>awk '{print $3}' $filename
+# Prints field #3 of file $filename to stdout.
 
-awk '{print $1 $5 $6}'
-# Prints fields #1, #5, and #6.</programlisting></para> 
+awk '{print $1 $5 $6}' $filename
+# Prints fields #1, #5, and #6 of file $filename.</programlisting></para> 
 
      <para>We have just seen the awk <command>print</command> command
        in action. The only other feature of awk we need to deal with
@@ -20469,8 +20949,8 @@ awk '{print $1 $5 $6}'
      <para><programlisting>{ total += ${column_number} }</programlisting>
        This adds the value of <emphasis>column_number</emphasis> to
        the running total of <quote>total</quote>. Finally, to print
-       <quote>total</quote>, there needs to be an <command>END</command>
-       command to terminate the processing.
+       <quote>total</quote>, there is an <command>END</command> command
+       block, executed after the script has processed all its input.
        <programlisting>END { print total }</programlisting></para>
 
      <para>Corresponding to the <command>END</command>, there is a
@@ -20491,6 +20971,7 @@ awk '{print $1 $5 $6}'
          <listitem><para><xref linkend="blotout"></para></listitem>
          <listitem><para><xref linkend="seedingrandom"></para></listitem>
          <listitem><para><xref linkend="idelete"></para></listitem>
+         <listitem><para><xref linkend="substringex"></para></listitem>
        </orderedlist>
       </para>	 
 
@@ -20878,6 +21359,71 @@ read -p "$(gettext -s "Enter the value: ")" var
 
 
 
+  <appendix id="histcommands">
+      <title>History Commands</title>
+
+     <para>The Bash shell provides command-line tools for editing and
+       manipulating a user's <emphasis>command history</emphasis>. This
+       is primarily a convenience, a means of saving keystrokes.</para>
+
+     <para>Bash history commands:
+       <orderedlist>
+         <listitem><para><command>history</command></para></listitem>
+         <listitem><para><command>fc</command></para></listitem>
+       </orderedlist>
+     </para>  
+
+	  <para>
+	      <screen><prompt>bash$ </prompt><userinput>history</userinput>
+<computeroutput>   1  mount /mnt/cdrom
+    2  cd /mnt/cdrom
+    3  ls
+     ...</computeroutput>
+	      </screen>
+	    </para>
+
+     <para>Internal variables associated with Bash history commands:
+       <orderedlist>
+         <listitem><para>$HISTCMD</para></listitem>
+         <listitem><para>$HISTCONTROL</para></listitem>
+         <listitem><para>$HISTIGNORE</para></listitem>
+         <listitem><para>$HISTFILE</para></listitem>
+         <listitem><para>$HISTFILESIZE</para></listitem>
+         <listitem><para>$HISTSIZE</para></listitem>
+         <listitem><para>!!</para></listitem>
+         <listitem><para>!$</para></listitem>
+         <listitem><para>!#</para></listitem>
+         <listitem><para>!N</para></listitem>
+         <listitem><para>!-N</para></listitem>
+         <listitem><para>!STRING</para></listitem>
+         <listitem><para>!?STRING?</para></listitem>
+         <listitem><para>^STRING^string^</para></listitem>
+       </orderedlist>
+     </para>  
+
+     <para>Unfortunately, the Bash history tools find no use in scripting. 
+        <programlisting>#!/bin/bash
+# history.sh
+# Attempt to use 'history' command in a script.
+
+history
+
+# Script produces no output.
+# History commands do not work within a script.</programlisting>
+     </para>
+
+	  <para>
+	      <screen><prompt>bash$ </prompt><userinput>./history.sh</userinput>
+<computeroutput>(no output)</computeroutput>	      
+	      </screen>
+	    </para>
+
+
+
+  </appendix>
+    <!-- History Commands -->
+
+
   <appendix id="sample-bashrc">
       <title>A Sample <filename>.bashrc</filename> File</title>
 
@@ -21591,11 +22137,11 @@ Smith,Tom,404 Polk Ave.,Los Angeles,CA,90003,(213) 879-5612
 
     <para>Hyun Jin Cha has done a <ulink
       url="http://kldp.org/HOWTO/html/Adv-Bash-Scr-HOWTO/index.html">Korean
-      translation</ulink> of an earlier version of this book.
-      A Portuguese translation will soon commence.  If you wish to
-      translate it into another language, please feel free to do so,
-      subject to the terms stated above. The author would appreciate
-      being notified of such efforts.</para>
+      translation</ulink> of an earlier version of this book.  Spanish,
+      Portuguese, and French translations are underway. If you wish to
+      translate this document into another language, please feel free
+      to do so, subject to the terms stated above. The author would
+      appreciate being notified of such efforts.</para>
 
     <para>If this document is printed as a hard-copy book, the author
       requests a courtesy copy. This is a request, not a requirement.</para>
diff --git a/LDP/guide/docbook/abs-guide/ex56.sh b/LDP/guide/docbook/abs-guide/ex56.sh
index 5ae8877e..ad156fb1 100644
--- a/LDP/guide/docbook/abs-guide/ex56.sh
+++ b/LDP/guide/docbook/abs-guide/ex56.sh
@@ -4,7 +4,7 @@
 echo "This precedes the embedded Perl script within \"$0\"."
 echo "==============================================================="
 
-perl -e 'print "This is an embedded Perl script\n"'
+perl -e 'print "This is an embedded Perl script.\n";'
 # Like sed, Perl also uses the "-e" option.
 
 echo "==============================================================="
diff --git a/LDP/guide/docbook/abs-guide/ex62.sh b/LDP/guide/docbook/abs-guide/ex62.sh
index 5415027e..4658e8c5 100644
--- a/LDP/guide/docbook/abs-guide/ex62.sh
+++ b/LDP/guide/docbook/abs-guide/ex62.sh
@@ -2,17 +2,24 @@
 
 func ()
 {
-  local a=23
-  echo
-  echo "a in function = $a"
+  local loc_var=23       # Declared local.
   echo
+  echo "\"loc_var\" in function = $loc_var"
+  global_var=999         # Not declared local.
+  echo "\"global_var\" in function = $global_var"
 }  
 
 func
 
 # Now, see if local 'a' exists outside function.
 
-echo "a outside function = $a"  # Nope, 'a' not visible globally.
 echo
+echo "\"loc_var\" outside function = $loc_var"
+                                      # "loc_var" outside function = 
+                                      # Nope, $loc_var not visible globally.
+echo "\"global_var\" outside function = $global_var"
+                                      # "global_var" outside function = 999
+                                      # $global_var is visible globally.
+echo				      
 
 exit 0
diff --git a/LDP/guide/docbook/abs-guide/ex9.sh b/LDP/guide/docbook/abs-guide/ex9.sh
index 5340c515..30d511c7 100644
--- a/LDP/guide/docbook/abs-guide/ex9.sh
+++ b/LDP/guide/docbook/abs-guide/ex9.sh
@@ -25,9 +25,15 @@ echo ${hello} #Identical to above.
 echo "$hello"
 echo "${hello}"
 
-# hello="A B  C   D"
+echo
+
+hello="A B  C   D"
+echo $hello
+echo "$hello"
 # Now,   echo $hello   and   echo "$hello"   give different results.
-# Quoting variable preserves whitespace.
+# Quoting a variable preserves whitespace.
+
+echo
 
 echo '$hello'
 #  Variable referencing disabled by single quotes,
diff --git a/LDP/guide/docbook/abs-guide/symlinks.sh b/LDP/guide/docbook/abs-guide/symlinks.sh
index b8f4ae21..5d93084b 100644
--- a/LDP/guide/docbook/abs-guide/symlinks.sh
+++ b/LDP/guide/docbook/abs-guide/symlinks.sh
@@ -12,10 +12,10 @@ fi
 
 echo "symbolic links in directory \"$directory\""
 
-for file in $( find $directory -type l )   # -type l = symbolic links
+for file in "$( find $directory -type l )"   # -type l = symbolic links
 do
   echo "$file"
-done | sort                                # Otherwise file list is unsorted.
+done | sort                                  # Otherwise file list is unsorted.
 
 #  As Dominik 'Aeneas' Schnitzer points out,
 #+ failing to quote  $( find $directory -type l )
diff --git a/LDP/guide/docbook/abs-guide/symlinks2.sh b/LDP/guide/docbook/abs-guide/symlinks2.sh
index 2171812e..7572581c 100644
--- a/LDP/guide/docbook/abs-guide/symlinks2.sh
+++ b/LDP/guide/docbook/abs-guide/symlinks2.sh
@@ -13,10 +13,10 @@ fi
 
 echo "symbolic links in directory \"$directory\""
 
-for file in $( find $directory -type l )   # -type l = symbolic links
+for file in "$( find $directory -type l )"   # -type l = symbolic links
 do
   echo "$file"
-done | sort > "$OUTFILE"                   # stdout of loop
-#           ^^^^^^^^^^^^                     redirected to save file.
+done | sort > "$OUTFILE"                     # stdout of loop
+#           ^^^^^^^^^^^^                       redirected to save file.
 
 exit 0
diff --git a/LDP/guide/docbook/abs-guide/weirdvars.sh b/LDP/guide/docbook/abs-guide/weirdvars.sh
index 847b9745..c1a9a24a 100644
--- a/LDP/guide/docbook/abs-guide/weirdvars.sh
+++ b/LDP/guide/docbook/abs-guide/weirdvars.sh
@@ -5,9 +5,11 @@ var="'(]\\{}\$\""
 echo $var        # '(]\{}$"
 echo "$var"      # '(]\{}$"     Doesn't make a difference.
 
+echo
+
 IFS='\'
-echo $var        # '(]\{}$"     \ converted to space.
-echo "$var"      # '(] {}$"
+echo $var        # '(] {}$"     \ converted to space.
+echo "$var"      # '(]\{}$"
 
 # Examples above supplied by S.C.