Managing NFS and NIS, 2nd Edition
by Hal Stern, Mike Eisler, Ricardo Labiaga


The unconfirmed error reports are from readers.  They have not yet been 
approved or disproved by the author or editor and represent solely the
opinion of the reader.

Here's a key to the markup:
        [page-number]: serious technical mistake
        {page-number}: minor technical mistake
        <page-number>: important language/formatting problem
        (page-number): language change or minor formatting problem
        ?page-number?: reader question or request for clarification

This page was updated June 16, 2008.


UNCONFIRMED  errors and comments from readers: 


{18} 4th paragraph;
The 1st sentence of the 4th paragraph should say "Instead of using ..., RPC servers are designated by program number." The original sentence said "service number".


(19)  End of third sentence in "Socket RPC and Transport Independent RPC" section;
Remove few extra words at the end of the sentence:

   ... transition RPC applications was needed.

=>

   ... transition RPC applications.

As a result, the entire sentence reads:

The motivation for TI-RPC was that it appeared that OSI networking
would eventually supplant TCP/IP-based networking, and so a
transport independent interface would make it easier to transition
RPC applications.


(27) 1st paragraph, 2nd line;
change "each database, which" to "each database"


(142)  4th paragraph, 2nd line;
/var/statmom/sm should be /var/statmon/sm


(177)  5th paragraph (numbered 6.);
/tmp_mnt/news should be /tmp_mnt/tools/news


{183}  Last bullet point;
"Even though the corresponding map names in NIS are auto_direct and auto_home..."

Shouldn't this be auto.direct and auto.tools?


{200}  numbered bullet '3.' at bottom of page;
If I am understanding the heirchical mounts (in non -hosts maps - pg. 199) correctly, then the auto_tools entry below should be cha
nged to referenece a different NFS mount and NOT the same as the root of the hierarchical mount.  If I am missing something, please
 explain.

currently:

deskset   / -ro,intr mahimahi:/tools2/deskset \
               /wonderworks-v2.0 -ro,intr mahimahi:/tools2/deskset

should be:

deskset   / -ro,intr mahimahi:/tools2/deskset \
               /wonderworks-v2.0 -ro,intr     \
               wahoo:/export/tools/deskset/wonderworks-v2.0


{200}  3. Change the deskset entry in the auto_tools map to:;
I believe the listing under subparagraph 3. should be 

deskset   / -ro,intr mahimahi:/tools2/deskset \
             /wonderworks-v2.0 -ro,intr wahoo:/tools2/deskset
                                        ^^^^^

The book list mahimahi instead of wahoo.


[229]  6th non-courier paragraph, starting 'The first example trusts...';
"The third example is most restrictive.  Only user johnc is trusted on host corvette,
and of course both luser and ruser (both "johnc") must be the same."

On Solaris 8 and and 9 (and perhaps previous versions) this is untrue.

If /etc/hosts.equiv contains

  hostname rusername

then the named ruser can claim to be *any* luser, including root,
on the trusting host.

E.g., on host 'mine', /etc/hosts.equiv says

  jim  mud

Then user jim, on host mud, can pretend to be anyone at all on
host mine.

This is potentially lethal.


[307]  1/2 way down the page;
Half way down the page, a new subsection starts entitled
"RPC Portmapper _ rpcbind".

Is that formatting correct? I expect to to see one of:

(a) RPC portmapper (rpcbind)
(b) RPC portmapper - rpcbind

preferably the first one.