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 |
| Printed |
Page xi
1st paragraph, 2d line |
the two instances of "knows" should be "know" - as in "you...know"
|
Anonymous |
| Printed |
Page 14
2nd Paragraph from the bottom. bin, etc, users,... |
The fragment: "they usually contain specific XML (Extensible Markup Language) option
spelling(kinds) of system files."
This just doesn't make any sense to me!
|
Anonymous |
| Printed |
Page 14
2nd paragraph from bottom |
"option (spelling)kinds" should probably read "files
special
kinds": the "option (spelling)" being a missing word followed by the written
description of an option-hyphen, or two words linked by an option-hyphen witho
ut any
spaces, in either case marked as a spelling error by some software...
|
Anonymous |
| Printed |
Page 21
Third text paragraph |
"There may also be other files, such as .tcshr or .execrc" .tcshr sould be .tshrc.
|
Anonymous |
| Printed |
Page 23
last paragraph |
GNU.org does not appear to have "ls" as a separate download...
|
Anonymous |
| Printed |
Page 37
3rd paragraph |
The commands to be typed for converting from Mac-to-Unix ("m2u") and Unix-to-Mac
("u2m") look identical in their translation, specifically "tr ' 15' ' 12'".
|
Anonymous |
| Printed |
Page 37
3 |
===To reiterate the mistake for fixing the line return problem and to offer a
workaround for this important little snippit of code===
Manually open or create a new .cshrc file (in ~/ ) in vi and add the following
lines:
alias m2u tr " ' 15' ' 12' "
alias u2m tr " ' 12' ' 15' "
Save, quit and then type: source ~/.cshrc
It shoud now work as described in the following paragraphs. There may be a more
elegant solution, but this works for me.
|
Anonymous |
| Printed |
Page 37
3rd paragraph |
kinds" or "filesI was not able to get the command to work as shown in the boo kinds" or "filesk.
By adding backslashes and a quote around the command, I succeeded/
echo alias m2u \"tr \'\\015\\\' \'\\012\\\'\" >> ~/.cshrc
You may have a better way to do this, but the one shown in the book does not work.
|
Anonymous |
| Printed |
Page 39
last paragraph |
the phrase "has changed since you started vi" appears to be extraneous, but is at
least confusing without additional punctuation & wording, such as: "bottom of the
display which has changed since you started vi - and is sitting"...
|
Anonymous |
| Printed |
Page 41
Table at bottom of page |
Table 3-1 is a list of common vi editing commands. I was using this for reference and
wondering why there was no command to delete a character in vi. A friend told me the
correct command was 'x'. When I looked to find this in the table, it wasn't there. It
appears that the table ends rather abruptly at "O" - there are no commands commencing
with letters after O in the alphabet. It appears as part of the table has been left
out.
|
Anonymous |
| Printed |
Page 41
3rd paragraph |
VIM.org is down, but the page redirects to vim.SourceForge.net with good
information...
{45/46} In "Learning Unix for Mac OS X" by Dave Taylor and Jerry Peek, printed May 2002,
there are a couple of corrections required in Chapter 3 - File Management.
In the 'Managing Your Files' section, on pages 45 and 46, there are references
to listing /rsrc files. The body text, and also the sample commands, interchange
between this and /rscr, whilst providing output related to /rsrc files. Given
that Unix/Darwin is unforgiving towards spelling errors, this could cause a
little trouble for beginning users.
|
Anonymous |
| Printed |
Page 44
last paragraph, it says you need CpMac to correctly |
copy a MacOS X application such as Chess. This is completely wrong.
First of all, Chess is called "Chess.app", not "chess.app" - this
makes a difference when you use UFS (not HFS+), as many Unix
inclined MacOS X users will do, and is confusing in any case.
Second, and most important, Chess.app is an *application bundle*,
which from Unix's perspective is simply a directory, nothing more.
Therefore, you don't need CpMac at all to copy Chess; cp -R
Chess.app will work just fine, as with any other directory.
Third, Chess.app is a Cocoa app. Cocoa apps are the future of MacOS
X and as such do not have any resource forks, so even if you only
wanted to copy some discrete files from within Chess.app, you'd
never need to use CpMac.
Forth, on UFS you *never* need to use CpMac, because the resource
fork of MyFile is simply another plain Unix file called ._MyFile.
So all resource forks of files within a directory will be copied
correctly when you cp -R the directory. The *ONLY* thing you have
to pay attention to while working on UFS is when you copy a file
(or directory) by itself that has a ("top level") resource fork; in
this case, you'll have to remember to additionally copy ._MyFile.
Fifth, the *ONLY* situation where you need to use CpMac (or MvMac,
for that matter) is when you copy (a) file(s) with a resource fork
on HFS+. Note that resource forks are deprecated on MacOS X; they
are leftovers from the Classic MacOS and will mainly appear in
Classic and Carbon apps. (Unfortunately, the Finder [a Carbon app
itself, alas] still uses resource forks for file icons and file
attributes such as Hide, so CpMac might be needed in this case,
too.)
|
Anonymous |
| Printed |
Page 78
Footnote |
The "File and Directory Wildcards" is in chapter 3, not chapter 4.
|
Anonymous |
