UNIX Power Tools, 2nd Edition
by Jerry Peek, Tim O'Reilly, and Mike Loukides


Here are the changes that were made in the 7th printing (indicated by
"0 9 8 7" on the copyright page):


(xxxix) The following names were added to the page:

	CY   Chuck Yerkes        13.15

        EM   Evan L. Marcus      13.15


(214) 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 &


{216} The last line of code, on the right hand side read:

	...bash

The line now reads:

	...bash, ksh


(223) 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):


(226) All lines in the second column in the middle of the page now line 
      up underneath each other.


(261) 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 (.):


(264) 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.)


{296} The second paragraph in article 17.08 now begins:
	
	Newer versions....

The first example and the paragraph after it read:

        % touch 03201600 /tmp/4PMyesterday

    Then to find the files created after this, give the command:

They now read:

        % touch -t 03201600 /tmp/4PMyesterday

    (Some versions of \fItouch\fP don't need the \fI\-t\fP option.)
    Then to find the files created after this, give the command:


{297} At the top of the page, the first two code lines now have a 
      -t before the number in each:

    % touch -t 0703104682 /tmp/file1
    % touch -t 0804213785 /tmp/file2


{366} The last sentence read:

    If your version can do that, the syntax is probably like this:

        % touch date filename1 filename2 ...

It now reads:

    If your version can do that, the syntax is probably like this
    (though your version may not need the \fI\-t\fP):

        % touch -t date filename1 filename2 ...


(367) Second line, the "yy" at the end of "modyhrmiyy" has been deleted
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:


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