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 50
5th paragraph (paw print "tip") |
Page 50 states that "Information on customizing your path is
found in the section "Customizing your shell environment" in
Chapter 4, however there are no examples for customizing the path.
The following should be a new subsection, on or around page 61,
for "Customizing your Path":
To modify the PATH so that your changes are loaded each time you launch
the Terminal application, edit the .login file in your home directory
(~/.login) and add the following line:
set path = ( <new-location1> <new-location2> $path )
as in:
set path = ( $HOME/bin /Developer/Tools $path )
After you save changes, quit the Terminal application and restart it.
If you echo the $PATH variable, you should see the new entries:
[Brian-Jepsons-Computer:~] bjepson% echo $PATH
/Users/bjepson/bin:/Developer/Tools:/bin:/sbin:/usr/bin:/usr/sbin
|
Anonymous |
|
|
| Printed |
Page 91-92
the section on Lynx starts by suggesting that the |
reader install it. I've been in touch with a reader who did that
and ran into problems. The problem was that the installer put
the lynx binary somewhere that wasn't on the shell's search path.
So he got "lynx: command not found".
As it turns out, the reader's lynx went into the directory
/usr/local/bin. Dave told me that *his* Lynx went into /sw/bin.
I don't know how often Apple will change its mind ;-) about the
location of Lynx. But, if the second edition still mentions it,
the reader will need help to locate and run the program! Dave
suggested making an alias (which the book tells how to do, I think).
An answer that might be worth mentioning -- especially if the reader
will be installing other software that goes into /usr/local/bin --
is to use the following command in .tcshrc instead of an alias:
set path = ($path /usr/local/bin)
(That could possibly mean that the user will have /usr/local/bin
added several times to the end of the path during a session...
because each subshell reads .tcshrc, and a parent process may
already have read it and added the directory to the end. But,
because tcsh hashes the list of programs from the path, it
shouldn't be a problem.)
|
Anonymous |
|
|
| Printed |
Page 125
Mail cannot be sent directly from the command line, though, user has |
followed the instructions given on page 125 of your book "unix for mac OSX"
"All you need to do is change the permission of te root directory with
chmod etc."
[k04_050_xce2003:~] mcbeen% sudo chmod 755 /
Password:
[k04_050_xce2003:~] mcbeen% mail jbeentjes@mac.com
Subject: u
uuuu
.
EOT
[k04_050_xce2003:~] mcbeen% can not chdir(/var/spool/clientmqueue/):
Permission denied
Program mode requires special privileges, e.g., root or TrustedUser.
[k04_050_xce2003:~] mcbeen% cd /var/spool/clientmqueue/
[k04_050_xce2003:/var/spool/clientmqueue] mcbeen% ll
total 0
drwxrwx--- 2 root wheel 264 May 23 03:56 .
drwxr-xr-x 9 root wheel 264 Oct 23 2001 ..
[k04_050_xce2003:/var/spool/clientmqueue] mcbeen%
Follow this URL for a discussion of the reasons and a resolution to this
issue:
http://www.macdevcenter.com/pub/a/mac/2002/06/07/sendmail_1015.html
|
Anonymous |
|
|