The errata list is a list of errors and their corrections that were found after the product was released.
The following errata were submitted by our customers and have not yet been approved or disproved by the author or editor. They solely represent the opinion of the customer.
| Version |
Location |
Description |
Submitted by |
Date submitted |
| Printed |
Page 9
"general note" box |
Forward reference...
The tip refers to "shell escape sequences described earlier". They're actually
described later in the book, on p14.
|
Anonymous |
|
| Printed |
Page 12
penultimate paragraph |
"fikle" should be "file".
|
Anonymous |
|
| Printed |
Page 29
I think there's a very minor error on p. 29 of the book. The description |
of scp reads, "Secures alternative to rcp," but probably should read,
"Secure alternative to rcp."
|
Anonymous |
|
| Printed |
Page 31
2nd paragraph |
strings(1) is described as "A tool that searches binary files for text patterns".
This is misleading; strings has no pattern-matching capability. Rather, it
finds sequences of printing characters that end in newlines or nulls.
It should also be noted that strings is ASCII-specific and will not, AFAIK,
recognize arbitrary Unicode strings.
|
Anonymous |
|
| Printed |
Page 44
Figure 3-2 |
PAM and CDSA do not sit on top of DirectoryServices. PAM sits on top of
SecurityServer, although in the future it may sit on top of DirectoryServices for
password changing. (For password changing, as shipped, PAM will only talk to NetInfo
directly; but confusingly this functionality is not used in Jaguar.)
In turn, the SecurityServer uses DirectoryServices to perform user authentication.
CDSA is a component of the Security services.
One of the confusing issues is that, from Jaguar, some OS X applications (such as
loginwindow) have apparently started to use DirectoryServices directly where they
once would have used the UNIX C library API. As such, directory services (such as
NIS) that are supported in lookupd by not DirectoryServices are problematic to
integrate.
|
Anonymous |
|
| Printed |
Page 49
niutil makes an appearance on p. 49 (twice, actually), but doesn't appear |
in Table 3-1 and doesn't come up again in the chapter.
|
Anonymous |
|
| Printed |
Page 70
before "The First Line of Defense" (:-) |
Actually, this is neither a "reader request", nor a "request for clarifiaction",
but the menu above has no item for "enhancement request". Sigh.
Anyway, in any discussion of unpacking generic tar(1) archives on OSX,
the case insensitivity of HFS+ should be pointed out (preferably with one
of your "bear trap" icons. Otherwise, the unsuspecting user is all too likely
to lose files (e.g., when a directory within a tarball contains both Makefile
and makefile).
More generally, I'd like to see some detailed coverage of how to write
safe shell scripts under Mac OS X (possibly beginning with the advice
"use perl, instead" :-). For instance, it can be quite tricky to handle the
sorts of oddball characters OSX puts into path names. Although there
is a bit of discussion about this on page 14, but it doesn't go nearly far
enough...
|
Anonymous |
|
| Printed |
Page 132
2nd para under "fs_usage" |
"Figure 8-2 shows the output of fs_usage"... no it doesn't. Fig 8-2 shows sc_usage,
and is correctly referenced from the description of sc_usage. The fs_usage figure is
missing.
|
Anonymous |
|