Errata


Print Print Icon

Submit your own errata for this product.


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 "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



Version Location Description Submitted By Corrected
Printed Page ..
will go no father than [..]

should be

Anonymous 
Printed Page ..
will go no farther than [..]

Anonymous 
Printed Page 3
2nd paragraph

"orwere" should be "or were"

Note from the Author or Editor:
correct.

Anonymous 
Printed Page 27
3rd para

looked an example
should be
looked at an example

Anonymous 
Printed Page 42
last oaragraph "ACLs in the superblock"

..."For example to enable ACLs on the /home filesystem, you would unmount it, and run
tunefs -a /home."...

Should be

..."For example to enable ACLs on the /home filesystem, you would unmount it, and run
tunefs -a enable /home."...
^^^^^^

Anonymous 
Printed Page 50
Paragraph about Random PIDs

a "been" is missing in:

A number of exploits, such as race conditions, make use of the fact that process IDs (PIDs) have historically <here> issued sequentially by the operating system.

Note from the Author or Editor:
correct.

Anonymous 
Printed Page 61
1st paragraph

"When we text say chroot..."
should read:
"When we say chroot..."

Anonymous 
Printed Page 99
1st para, 2nd dot point

ask a
should be
as a

Anonymous 
Printed Page 110
1st paragraph

"For more information about PAM and login classes."
should read:
"For more information about PAM and login classes, please refer to the
pam(8) and login.conf(5) manpages."

Anonymous 
Printed Page 130
2nd paragraph

[..] will go no father than [..]

should be

[..] will go no farther than [..]

Note from the Author or Editor:
Correct.

Anonymous 
Printed Page 130
2nd paragraph

Anonymous 
Printed Page 130
Last para (note)

form, which
should be
from which

Anonymous 
Printed Page 150
paragraph starting with 'The latter lines...'

dip.t-dailin.net should be dip.t-dialin.net (not only because the latter is mentioned in example 4.7 but also because that's the correct address that german telekom assign to their clients)

Anonymous 
Printed Page 159
Example 4.10

Judging by the shebang line, the script is supposed to be a Bourne Shell script.

However, neither the lines

level1_sys=alpha beta gamma delta
level2_sys=mercury venus earth mars

nor

foreach system in $level1_sys; do

are valid Bourne Shell (or ksh or bash) syntax.

Note from the Author or Editor:
These are syntax errors. Two lines need double quotes:
level1_sys="alpha beta gamma delta"
level2_sys="mercury venus earth mars"

The other line should read:
for system in $level1_sys; do

Anonymous 
Printed Page 176
4th para

trying deliver
should be
trying to deliver

Anonymous 
Printed Page 183
Last sentence

Even since
should be
Ever since

Anonymous 
Printed Page 189,193
Last paragraph on each page

BIND 9 has replaced BIND 8.3.1-REL as the included name server software
as of FreeBSD 5.3-RELEASE. It is now chrooted by default.

Anonymous 
Printed Page 221
4th para

the To: line
should be
the From: line

Anonymous 
Printed Page 318
1st para

rc.firewall to
should be
rc.firewall too

Anonymous 
Printed Page 367
2nd paragraph

> The manual page for syslog.conf(5) specifies that these facilities are for local use.

The manual page for syslog.conf(5) does not actually mention the purpose of local[0-7], the one for syslog(3) does, however:

LOG_LOCAL0 Reserved for local use. Similarly for LOG_LOCAL1 through LOG_LOCAL7.

> You, the administrator, may define these seven facilities [..]

Unless local0 has a special meaning there are eigth of them.

Note from the Author or Editor:
This is correct. There are 8 facilities LOCAL0 through LOCAL7 and they are documented in the syslog(3) man page.

Anonymous 


"...a worthy addition to system administrators' book shelves. Korff, Hope & Potter have produced a book that should help administrators secure their systems both now and in the future."
--David Bogan, Daemonnews.org