Time Management for System Administrators
by Thomas A. Limoncelli

The unconfirmed error reports are from readers.  They have not yet been 
approved or disproved by the author or editor and represent solely the
opinion of the reader.

Here's a key to the markup:
        [page-number]: serious technical mistake
        {page-number}: minor technical mistake
        <page-number>: important language/formatting problem
        (page-number): language change or minor formatting problem
        ?page-number?: reader question or request for clarification

This page was updated June 17, 2008.


UNCONFIRMED  errors and comments from readers: 


{130} "Delete or forward, then delete";
pg 130 (Ch 10, Email Management, "Delete or forward, then delete")

I also don't reply to emails spreading the latest hilarious Internet
joke - such as when I learned about a seven-year-old boy in England,
named Craig Shergold, trying to get into the _Guiness_Book_Of_World_
_Records_ by amassing the largest postcard collection. Oh wait, that's
an urban legend.

It isn't an urban legend; it is a real story that is no longer relevant because he made the record.

I would change:
Oh wait, that's an urban legend.
to
Oh wait, he's no longer collecting them.


{174} makeimage1 script example;
http://www.oreilly.com/catalog/timemgmt/errata/timemgmt.307 states:

> ########################################
>
> {175} line 1, line 4, line 5
>
> $*
> ->
> $@
>
> (three occurrences)
>
> ########################################

pg 175, line 1, (corrected) thus reads:

> The $@ in the makeimage1 script...

The other two occurrences cited in the above correction likewise refer to the same script (bottom of 174).

However, while the description of the makeimage1 script on 175 was updated in 3/07, the script itself was not updated, and still reads:

> mkisofs _D -l -J -r -L -f -P "Limoncelli" -V `date -u %m%d` $*

The "$*" at the end of the script should, it would therefore seem, be changed to "$@", in keeping with 3/07 {175} line 1, line 4, line 5. (The same error appears to have also been corrected in 3/07 {175} code example, line 1 and 3/07 {177} code example, line 1.)