Errata

Here's a list of authors, their initials, and the articles they wrote
or contributed to:

CY Chuck Yerkes 13.15

EM Evan L. Marcus 13.15

The text used to read:

"stty eraseZ"

It now reads:

"stty erase Z"

"A lot of 'oddball' time zones are included: for example, the state
of Indiana, for which large parts observe Daylight Saving Time ..."

changed to

"A lot of 'oddball' time zones are included: for example, the state
of Indiana, which large parts of which don't observe Daylight Saving
Time ..."

"See " has been deleted

The first paragraph has been changed to now read:

You don't need to look up the job number to select a job, though.
Instead, you can specify a job by name. Simply use the first
letter(s) of the command name--enough to be unambiguous--after the
percent sign. For example, the commands above could have been
issued as:

% kill %n
% fg %vi

Also, the line after the second code example that read:

"to kill the nroff job shown in the example above"

has been deleted.

And, the last paragraph in the article, used to read:

You can put a stopped job into the background in a similar way.
For example:

% %2 &

will put job number 2 into the background.

It now reads:

You can put a stopped job into the background in a similar way.
For example, to put job number 2 into the background, add an
ampersand:

% %2 &

The next-to-last paragraph, from the second line on read:

Here's how to run your cruncher program, route the stderr through
a pipe to the mail program, and leave stdout going to your screen:

It now reads:

Here's how to run your cruncher program, route the stderr through
a pipe to the mail program, and leave the stdout going wherever it
was going (in this case, to your screen):

up underneath each other.

at the end of p. 228

The text used to read:

"csh and bash have pushd and popd commands make this a lot easier."

It now reads:

"csh and bash have pushd and popd commands to make this a lot easier."

changed:

"doesn't match xabcx or xabcabcx, but does match"

to:

"doesn't match xabcx, but does match"

A little more than half way down the page, a line read:

With some C shells (but not all), you don't need the trailing dot (.):

It now reads:

With some shells (but not all), you don't need the trailing dot (.):

The last paragraph now reads:

(Two notes: First, some UNIXes don't update the last-access time
of executable files (21.05) when you run them. Shell scripts are
always read, so their last-access times are always updated. Second,
for some bizarre reason, on systems I've seen, adding -u by itself
doesn't change the sorting order of ls -l; you also need -t, as in
ls -lut. Even more bizarre, on many systems--but not all--you don't
need -t to sort output by -c; simply type ls -lc.)

"when the file was created" to "when a link was added"

so the sentence now reads:

The inode time tells when a link was added, when you used
chmod to change the permissions, and so on.

The access time is the last time the file was read or written.

to:

The access time is the last time the file was read.

so it now reads:

modyhrmi

The "yy" paragraph has been deleted and the following paragraph has replaced it:

You can specify the number of seconds and the year (see your
touch(1) manual page). Note: older versions of touch without the -t
option, may have a different time format. For example, to make a
file named foo dated 4 p.m., March 20 of this year, give the command:

The next paragraph, beginning, "If you don't want to use...." now reads:

Versions of touch without the -t option have a problem. If you
want to set the current (not a different) time and the filename
starts with a number, be careful. touch may think that the filename
is a time and give the error "date: bad conversion." To enter a
filename that starts with a digit, use a relative pathname that
starts with a dot(.)(1.21). For example to make a file 123456 in
the current directory with a current timestamp:

some UNIX systems"

Section 22.02, paragraph 2, line 5 read:

The second number specifies the permission.

It now reads:

The second number specifies the group's permission.

The text used to read:

"Or use ypcat group | grep 100..."

It now reads:

"[Or use ypcat group | grep 100..."

The text currently reads:

"Although we recommend that you do not use crypt to encrypt files more than
1k long."

It should read:

"We recommend that you do not use crypt to encrypt files more than
1k long."

now starts with "agrep")

Mike Loukides

"$@" 44.15

(959) Next to "somecmd:" the phrase "command not found" is now in Courier font.

out of itals

reads

1, 2 metacharacters, 463

The index entry under $ (dollar sign) used to read:

$@, 838, 842, 884, 899, 926

It now reads:

"$@", 838, 842, 884, 899, 926

troff code, causing them not to appear in the text. The entry now
appears as follow:

-ef option (System V), 700

(and then the page number)