Learning the bash Shell

Errata for Learning the bash Shell

Submit your own errata for this product.


The errata list is a list of errors and their corrections that were found after the product was released. If the error was corrected in a later version or reprint the date of the correction will be displayed in the column titled "Date Corrected".

The following errata were submitted by our customers and approved as valid errors by the author or editor.

Color Key: Serious Technical Mistake Minor Technical Mistake Language or formatting error Typo Question Note Update



Version Location Description Submitted By Date Submitted Date Corrected
Printed
Page 2
3rd Point in the Section "What Is a Shell?"

"(output to the file phonelist.sorted)" previously had a space between "phone" and "list.sorted". It NOW READS "phonelist.sorted".

Anonymous    Mar 01, 2006
Printed
Page 27
last sentence of page

"If you use neither vi or emacs": Change 'or' to 'nor'

Anonymous    Nov 01, 2008
Printed
Page 47
first example

$ fc -l cp > lastcommands$ vi lastcommands$ source lastcommands NOW READS: $ fc -l cp > lastcommands $ vi lastcommands $ source lastcommands

Anonymous    Mar 01, 2006
Printed
Page 63
2nd example line in the section "Variables and Quoting"

$ fred='Four spaces between these words.' previously had only a single space between "these" and "words". It NOW HAS four, as the output of the echo "$fred" statement on the next page shows.

Anonymous    Mar 01, 2006
Printed
Page 83
Figure 4-1

Figure 4-1 should be changed to match that in the 2nd Edition. Item b: source alice should read: alice Item c: source alice & should read: alice &

Anonymous    Nov 01, 2008
Printed
Page 87
5th paragraph, 3rd line of code sample

echo "alice: $*" NOW READS: echo "alice: $@"

Anonymous    Mar 01, 2006
Printed
Page 115
4th paragraph

"Task 5-1" should be "Task 4-1"

Anonymous  May 23, 2009  Sep 01, 2009
Printed
Page 144
Middle of the page

#Process the input files for filename in "$*"; do NOW READS: #Process the input files for filename in "$@"; do

Anonymous    Mar 01, 2006
Printed
Page 160
source listing block

for (( j=i; j < numvalues; j++ )); do if [ ${values[j]} -le ${values[$lowest]}; then lowest=$j fi done -> for (( j=i; j < numvalues; j++ )); do if [ ${values[j]} -le ${values[$lowest]} ]; then lowest=$j fi done

Anonymous    Apr 01, 2007
Printed
Page 207
middle of 2nd line of 2nd paragraph

where printed it's a bit like concatening the the results of plain ps must be it's a bit like concatening the results of plain ps

Anonymous  Sep 02, 2009  Sep 01, 2009
Printed
Page 223
second listing (right after "For example:") and third listing (right after

"listings that look like this:"); Both examples previously had .ps8 that shouldn't be there and should have had newlines after the command (in bold). This HAS BEEN CORRECTED. Also, there was previously an extra "x"; xxtrace NOW READS xtrace.

Anonymous    Mar 01, 2006
Printed
Page 260
second bullet point

The script was missing some newlines. The commands starting with "chown", "chmod" and "/bin/grep" NOW APPEAR on their own lines.

Anonymous    Mar 01, 2006