Errata

for third edition):

"...the original authors. This
includes Tim O'Reilly and Jerry
Peek, among others previously
mentioned, who contributed to
past additions."

NOW READS:
"...the original authors. These
include Tim O'Reilly and Jerry
Peek, among others previously
mentioned, who contributed to
past editions."

To get one of these programs, use our visit the web site:

NOW READS:
To get one of these programs, visit the web site:

for third edition):

"...the original authors. This
includes Tim O'Reilly and Jerry
Peek, among others previously
mentioned, who contributed to
past additions."

NOW READS:
"...the original authors. These
include Tim O'Reilly and Jerry
Peek, among others previously
mentioned, who contributed to
past editions."

To get one of these programs, use our visit the web site:

NOW READS:
To get one of these programs, visit the web site:

In this sentence:

"But there's a catch: the Mac uses a carriage return ASCII character 015 to mark the
end of each line,while Unix uses a linefeed (ASCII 012)."

The phrase "ASCII 015" should be in parentheses.

(12 (and others?)) command-line examples;
The Preface shows that this book uses both constant-width Italic and boldfaced
constant-width Italic in examples. If I understand the convention, then the user
input in the examples on this page (the filenames file.mac, file.unix, file1, file2,
file3) should be boldfaced.

There may be other cases of the same problem in articles taken directly from the
second edition. I don't think we used boldfaced constant-width italic in UPT2. So I
won't report every occurrence of this problem... but you might want to search for it.

Note from the Author or Editor:
There are actually two separate errata here:

- adding parentheses on page 11

- fixing the font on pages 11 and 12 (and maybe other pages)

I agree with both. They're a bit confusing but not urgent.

delete 'are' i.e., so it reads 'file, but not actually'

"Most" is spelled "mfost" in "...because it starts with the mfost specific part.."

Note from the Author or Editor:
Page 21, para 1, sentence 3, change mfost to most

The last paragraph refers to Figure 1-1 in the following sentence:

So, as Figure 1.1 shows, there are a total of nine mode bits (three for each class) that set the basic access permissions.
it should say:
So, there are a total of nine mode bits (three for each class) that set the basic access permissions.

(figure 1-1 is for something different, and the figures for permission bits were removed in the 3rd edition)

*******************************************

The last paragraph refers to Figure 1-1 in the following sentence:

So, as Figure 1.1 shows, there are a total of nine mode bits (three for each class) that set the basic access permissions.
it should say:
So, there are a total of nine mode bits (three for each class) that set the basic access permissions.

(figure 1-1 is for something different, and the figures for permission bits were removed in the 3rd edition)

*******************************************

In this sentence:

"Tcl is particularly prevelant
within Linux systems, though it's
use is widespread throughout all
Unix systems."

1)"Prevelant" HAS BEEN CHANGED to "prevalent".
2)"it's" HAS BEEN CHANGED to "its"

In this sentence:

"Tcl is particularly prevelant
within Linux systems, though it's
use is widespread throughout all
Unix systems."

1)"Prevelant" HAS BEEN CHANGED to "prevalent".
2)"it's" HAS BEEN CHANGED to "its"

In the sentence

"These three scripting languages seem so prevelant within the Unix world that I think
of them as the Unix Scripting language triumvirate."

either the word "Scripting" should start with a lowercase letter, or the phrase "Unix
Scripting language triumvirate" should have all words initial-capped.

are to an article that explains more about the concept or problem printed in gray."

The text is gray. But the article number reference, like (1.23), isn't there.

I thought this might be a problem in the PDF file, but the ch01.pdf file shows a link
properly. Since the sentence above is an introductory sentence meant to show an in-
sentence link, I've marked this as a (possible) serious problem.

Note from the Author or Editor:
Page 28, first para, first sentence, change to Unix Scripting Language Triumvirate.

Second problem, cannot locate the reference in the page, so cannot give directions to fix.

In this sentence:

"Unix boxes are, by default, characters-based systems."

I think that "characters-based" should be "character-based". At least, I've always
seen it written that way.

Note from the Author or Editor:
The reader is correct. But the article could use other changes on the same page. Please make the following three changes:


1) The change the reader suggested.


2) In the same paragraph, add a cross-reference to article 1.4 after "GUI". That is, the second sentence of the second paragraph should start this way:

"GUI (1.4) systems are added to facilitate..."

(Note that UPT uses automatic cross-references that fill in the article number at formatting time. Please don't type the 1.4 in literally; use a cross-reference instead.)


3) The third paragraph uses the incorrect term "X Windows". It also lists a website that doesn't exist anymore. Please revise the third (last) paragraph on page 31 to read:

"Though Darwin doesn't come with the X Window System, versions of X are available for Mac OS X."

stystems
should read:
systems

whitespce
should read:
whitespace

*******************************************

stystems
should read:
systems

whitespce
should read:
whitespace

*******************************************

Last paragraph reads:

"If you have ssh (1.21), its X forwarding..."

Maybe I just missed it in my quick scan through the book... but
it seems like there must be a better cross-reference for ssh
than article 1.21. Chapter 51 doesn't seem to introduce ssh and
its features (like X forwarding); if there isn't an overview of
ssh somewhere else, there should be.

Note from the Author or Editor:
I suggest changing this to:

"If you have ssh (51.2), its X forwarding..."

If there's another edition, it would be great to add an introductory ssh article that explains how to use ssh, redirect its input and output, suspend it with ~CTRL-Z, and so on. Some of this info is mentioned in parts of Chapter 51, but this is such an important program that an explicit intro would be good.

Footnote with "*", reads:

"Most of the recent distributions of Unix default to the use of
ssh as a secure replacement for the various r* command, (rsh, rcp,
rlogin, et al.), so you may want to skip ahead to Chapter 5."

That footnote has two typos. First, change "various r* command,"
to "various r* commands" (plural, and without the comma). Second,
"skip ahead to Chapter 5" should probably be changed to "skip
ahead to Chapter 51"... or maybe "skip back to Chapter 5"?

Also, the footnote doesn't make complete sense. Just because
Unix implementations replace r* commands with ssh, why should
readers skip to another chapter? Giving the chapter title, or
a brief description of the chapter, could help them understand.

Note from the Author or Editor:
The reader is correct, but this isn't an important problem. I suggest changing the footnote to read:

"Most of the recent distributions of Unix default to the use of
ssh as a secure replacement for the various r* commands (rsh, rcp,
rlogin, et al.). Chapter 51 introduces ssh."

Also, in the last paragraph on the page, beginning:

"If you have ssh (1.21), ..."

the xref should be to Chapter 51, probably article 51.2:

"If you have ssh (51.2), ..."

"take a peek at chapter Chapter 9."

'nuff said. ;-)

egrep output. It shouldn't.

Note from the Author or Editor:
The reader is correct. Please remove the blank line (between "AT&T Bell Labs" and "Symtel Labs of Chicago") from the example.

appear.

There are probably a few other places in the book that use the
same highlighting technique: one of the "diff" family (maybe
sdiff?), the "less" command, and something else. This might
be worth checking the whole book for.

Note from the Author or Editor:
The book uses Italics instead of highlighting, but it doesn't mention this. As the description says, there may be other places in the book with the same problem. (I don't think it's so serious, though, so I've reduced the classification from an "important" problem.)

The best solution would be to show hgrep output as it's shown in the second edition, article 27.20, page 491. (Maybe you could use a figure instead of plain text.) But if that's too hard to do, please add a sentence something like the following at the end of the first paragraph:

"(We've shown the highlighted strings in Italic text.)"

and also make "Italic text" in Italics.

If someone at O'Reilly could also flip through the second edition to see whether there are other places with this problem, it could save some confusion.

"But stil,automated deletion commands make me really nervous,..."

Change "stil" to "still".

Note from the Author or Editor:
The reader is correct. Please make this change.

named "bzip", but the text doesn't
describe it. ("gzip" has an icon
on the previous page. Maybe that's
what was meant to be here?) I'm
guessing that "bzip" should be
deleted.

Note from the Author or Editor:
The reader is correct. Please remove "bzip" from under the globe icon. (The globe icon should have only one line underneath it: "bzip2".)

Both "find" commands don't appear to have a space between them and the period/dot that follows. They appear as "find. | grep -v" when they should be "find . | grep -v"

"differences in word count between two files..."

change "differences" to "difference". (There's only one
difference between the two files.)

Note from the Author or Editor:
The reader is correct. Please make this change.

Change "demostration" to "demonstration"

*******************************************

Change "demostration" to "demonstration"

*******************************************

and

2nd line of paragraph that begins with 'Another solution ....'
change "heurestics" to "heuristics"

Note from the Author or Editor:
Page 393, change "lets" to let in first sentence, first para.

Page 393, change heurestics to heuristics in para 5, sentence 2

"To change all the files in the current directory to uppercase, try this..."
should be:
"To change all the files in the current directory to lowercase, try this..."

"To change all the files in the current directory to uppercase, try this..."
should be:
"To change all the files in the current directory to lowercase, try this..."

"...Unix is a mutliprocessing system."
should be:
"...Unix is a multiprocessing system."

"...Unix is a mutliprocessing system."
should be:
"...Unix is a multiprocessing system."

Note from the Author or Editor:
The reader is correct. Please make this change.

"This article tries to give you some background into, er, background processes."
should be:
"This article tries to give you some background on, er, background processes."

"This article tries to give you some background into, er, background processes."
should be:
"This article tries to give you some background on, er, background processes."

metaphors not metaphores

Note from the Author or Editor:
The reader is correct. Please make this change.

to "derivatives"

Note from the Author or Editor:
The reader is correct. Please make this change.

remove one of the 'the' between concatenating and results

Note from the Author or Editor:
The reader is correct. Please make the change listed under "Detailed description of error".

ststistics should be statistics

ststistics should be statistics

change configuring to configure

Note from the Author or Editor:
Please make the change given under "Detailed description of error".

With -i, cruncher lists ... should read
With -i, killall lists ...

Note from the Author or Editor:
Make the change as described under "Detailed description of error"

bols should be single straight
quotes. (See that same figure in
the second edition.)

bols should be single straight
quotes. (See that same figure in
the second edition.)

The word 'doesn't' previously appeared between
"workarounds" and "that." This HAS BEEN DELETED.

The word 'doesn't' previously appeared between
"workarounds" and "that." This HAS BEEN DELETED.

remove the word, doesn't

Note from the Author or Editor:
The reader is not correct; this is not an error. However, the article could be made clearer (and maybe it was confusing the reader).

Please change the last two sentences, which are currently:

"If this happens, use xargs (28.17). If your system doesn't have xargs, there are other workarounds that should solve the problem."

Replace them with these two sentences:

"If this happens, use xargs or a related solution. See article 28.17."

(NOTE: In case you aren't familiar with UPT formatting, the 28.17 should not be typed in literally. Instead, it should be a cross-reference that's automatically filled in with the proper article number as the page is formatted.)

NOW READS:
Part IV: Scripting

NOW READS:
Part IV: Scripting

Here are some general notes about runsed and about sed in general. These should be
mentioned either here or maybe in an earlier article like 32.2.

One advantage of editing with runsed, vs. writing a script for a scriptable editors
like ed and ex, is that there's no length limit to the file. If you want to edit a
3-terabyte text file, you can! (runsed assumes that the filesystem has enough free
space, though. If it doesn't, you'll need to hack runsed to put its temporary file
in another filesystem.)

Also, here's a new checksed. It accepts command-line options like -u, which it
passes to diff; this is handy if you want to use a "context diff", to control the
number of lines of context you see, and so on. This checksed doesn't have the
simplicity of the original version, so maybe it should be added as a supplemental
version.

#! /bin/sh
# $Id: checksed,v 1.2 2004/03/13 17:34:18 jpeek Exp $
#
# checksed - run 'sed -f sedscr' on a file and show diff of what it would do

diffopts=
script=sedscr

# Loop through command-line arguments.
# Print header before each file's results.
# Then run sed and show the changes script would make.
# Pipe the output of all commands to a pager (default: less).
for arg
do
# Grab any options for "diff". BUG: Doesn't handle option
# arguments like "-C 1". Option and argument can't have
# space between. You can use long options, though, like
# --context=2.
case "$arg" in
-*) diffopts="$diffopts $arg"; continue ;;
esac

echo "********** < = $arg > = sed output **********"
sed -f $script "$arg" | diff $diffopts "$arg" -
done | ${PAGER-less}

Here are some general notes about runsed and about sed in general. These should be
mentioned either here or maybe in an earlier article like 32.2.

One advantage of editing with runsed, vs. writing a script for a scriptable editors
like ed and ex, is that there's no length limit to the file. If you want to edit a
3-terabyte text file, you can! (runsed assumes that the filesystem has enough free
space, though. If it doesn't, you'll need to hack runsed to put its temporary file
in another filesystem.)

Also, here's a new checksed. It accepts command-line options like -u, which it
passes to diff; this is handy if you want to use a "context diff", to control the
number of lines of context you see, and so on. This checksed doesn't have the
simplicity of the original version, so maybe it should be added as a supplemental
version.

#! /bin/sh
# $Id: checksed,v 1.2 2004/03/13 17:34:18 jpeek Exp $
#
# checksed - run 'sed -f sedscr' on a file and show diff of what it would do

diffopts=
script=sedscr

# Loop through command-line arguments.
# Print header before each file's results.
# Then run sed and show the changes script would make.
# Pipe the output of all commands to a pager (default: less).
for arg
do
# Grab any options for "diff". BUG: Doesn't handle option
# arguments like "-C 1". Option and argument can't have
# space between. You can use long options, though, like
# --context=2.
case "$arg" in
-*) diffopts="$diffopts $arg"; continue ;;
esac

echo "********** < = $arg > = sed output **********"
sed -f $script "$arg" | diff $diffopts "$arg" -
done | ${PAGER-less}

On the 6th line of the sed script, an escaped slash(/) is missing inside the closing
HTML tag. It should be:
s/$/</h1>

On the 6th line of the sed script, an escaped slash(/) is missing inside the closing
HTML tag. It should be:
s/$/</h1>

1st line: "+case" should be "case"
2nd line: "vt100" should be "vt100)"

1st line: "+case" should be "case"
2nd line: "vt100" should be "vt100)"

"+if" should be "if"

(732 Footnote text on page 733 is
and 733 ) referenced on page 732

"+if" should be "if"

(732 Footnote text on page 733 is
and 733 ) referenced on page 732

... can handle arbitrary numbers of file descriptiors

should be

... can handle arbitrary numbers of file descriptors

Note from the Author or Editor:
Yes, this needs clarification. But the "Detailed description of error" doesn't clarify; the correction is the same as the original.

Please make the following edit. Replace the following text:

"3 through 9 (and bash and the other newer shells can handle arbitrary numbers of file descriptors, up to whatever ulimit -n happens to be set)."

with the following text:

"3 through 9. (Newer shells have higher limits. For instance, read the description of ulimit -n in the bash manual page.)"

NOTE that, as in the printed book, "ulimit -n" should be in a fixed-width font. Also, "bash" should be in Italics.

The example script is referred to as 'edmaster' until the middle of this page, when
it is suddenly referred to as 'edconfig'

Note from the Author or Editor:
Change the three occurrences of "edconfig" to "edmaster".

referred to article Chapter 39-

NOW REFERS to:
article 39.7

referred to article Chapter 39-

NOW REFERS to:
article 39.7

NOW READS:
This situation happens but not with some of the older, more system-specific makes.

NOW READS:
This situation happens but not with some of the older, more system-specific makes.

"Got to background"

NOW READS:
"Go to background".

"Got to background"

NOW READS:
"Go to background".

"-O": In the second column,
"Forces all documents into
specified" seems to be an incom-
plete phrase (into specified
*what*?).

Note from the Author or Editor:
In Table 40-2, in the 14th entry (for the option "-O or --output-document=file"), change the text in the "Purpose" column from:

"Forces all documents into specified"

to:

"Output all documents to the named file"

s/removed/remove/

"To removed an installed application..." should be "To remove an installed application"

interpretor

NOW READS:
interpreter

interpretor

NOW READS:
interpreter

ecclectic

NOW READS:
eclectic

ecclectic

NOW READS:
eclectic

bare

NOW READS:
bear

bare

NOW READS:
bear

intergers

NOW READS:
integers

intergers

NOW READS:
integers

"You may have notice that..."
should be:
"You may have noticed that..."

"You may have notice that..."
should be:
"You may have noticed that..."

"Example 41-7. Interating over a hash"
^
should be:
"Example 41-7. Iterating over a hash"

"Example 41-7. Interating over a hash"
^
should be:
"Example 41-7. Iterating over a hash"

"There are two ways of deferencing..."
should be:
"There are two ways of dereferencing..."

"There are two ways of deferencing..."
should be:
"There are two ways of dereferencing..."

There are two entries for the "less" pager:
"less command" and "less program".
They should be combined.

There are two entries for the "less" pager:
"less command" and "less program".
They should be combined.