Errata

Apache Jserv is referred to as "freeware" when it is in
fact using an OSI approved license, making it "open source software".

paragraph 4 states that /etc/services is consulted by getprotobyname().
the getprotobyname(3SOCKET) man page makes no reference to this. Shouldn't
that be /etc/inet/protocols / /etc/protocols, and not /etc/services? /etc/services is
consulted by the getservby*() functions. (test with truss)

paragraph 1: IPv6 TCP/UDP should use tcp6/udp6 as the protocol
names, not tcp/udp

bullet item 1 "support for single, dual, and quad _port_ ethernet
devices" would be clearer

last paragraph "connected using 10/100M cabling" should either
be "10/100Mb ethernet" or "CAT3/5 cabling". Page 57 subsequently references
"100M ethernet cable". 100M is not a cable type.

1st paragraph: if the host name lookup
fails, because the host is not found (NOTFOUND),
the local host file is NOT consulted if [NOTFOUND=return]
is used. To check the next available service, [NOTFOUND=return] should be taken OUT.

sentence after the first example: service
should be plural (netgroup and public key services).

bullet item two: Berkley Internet Daemon (BIND)
should be Berkley Internet Name Domain (BIND)

networks:byname should be networks.byname

{109/110}
no mention of userdel or groupdel (only
mentions manual deletion of users and groups)

bullet item 7: should read "installation OF setuid/setgid"

paragraph 3: "hole" should be "holes"

paragraph 2, last sentence: "declares" should be "declared"

Gb (gigabit) is used instead of GB (gigabyte)

table 7-1 domain logins should be domain logons

table 7-4, NFSERR_ISDIR A requested FILE exists as a directory (not files).

paragraph 4: sentence one should read something like "startup scripts
located in the /etc/init.d directory and
may be HARD linked FROM the appropriate rc directory (e.g., /etc/init.d/nfs.server
maybe be linked FROM /etc/rc2.d/S99nfs.server)." Solaris hard, not symbolically,
links startup scripts from the rcX.d directories, and the link target is what is
linked TO.

last paragraph: Sentence one should read something like "The dfmounts
COMMAND only provides details of remotely MOUNTED filesystems, and does not provide
details on user permissions on shared volumes"; it doesn't show any information about
shared filesystems unless they are actually mounted by a client. Also, in regards to
sentence two, the share command does NOT provide information about filesystems that
are currently remotely mounted; it shows shared filesystems, irrespective of whether
they are actually mounted or not.

command one: should have read:

mount -F nfs -o rw kiribati:/data /kiribati/data

the host name was left out

command four should really use '-F nfs' to mount only
NFS filesystems

paragraph 2: example file is called sum.txt in the text, e.txt
in the command example, and name.txt in the example's output

Gb (gigabit) is used instead of GB (gigabyte)

command example two: should specify that you need to cd to the /etc
directory

The last paragraph says "To copy the contents of a tape...", but uses the name of a
disk partition (/dev/rdsk/c0t0d2s1).

command example two: the * needs to be double quoted, else the list
of files in the current directory will be passed as arguments to the cpio command

crontab command examples: field five should be 0 for Sunday (and
all subsequent entries should have their fifth field decremented by one to
get Monday-Friday). 1 is for Monday.

last paragraph: the AMANDA backup software is "freeware", when
it should be called "Free Software", since it is an FSF approved Free Software
license.

paragraph 4, sentence one should have "user on the" before "system".

"The login shell specified must be listed in the /etc/shells file; otherwise, the
user will not be able to log in."

/etc/shells doesn't exist on our system, and anybody can log in.

Is this like the "allow"/"deny" files, where if the file isn't there, no check is
made?

paragraph two, sentence one: should read "...to be passed TO the class
C..."

paragraph two, sentence 3 is very unclear. Perhaps it should
just say "....administration facilities, the web server will be listening on this
port."

last paragraph, sentence 4 is extremely unclear. It seems
to imply that _TCP_ (packet) is *protected* by _UDP_ (datagram). Obviously,
this makes no sense.