🚀 go-pugleaf

   Fair enough.  I have the following entry in our netgroups map:

   physics		(annett.phys.psu.edu,,) (banavar.phys.psu.edu,,)\
		   (bangalore.phys.psu.edu,,) (collins.phys.psu.edu,,)\
		   (corsica.phys.psu.edu,,) (etat.phys.psu.edu,,)\
		   (faraday.phys.psu.edu,,) (glue.phys.psu.edu,,)\
		   (neutron.phys.psu.edu,,) (phoenix.phys.psu.edu,,)\
		   (psuphys1.phys.psu.edu,,) (quixote.phys.psu.edu,,)\
		   (color.phys.psu.edu,,) (willis.phys.psu.edu,,)

   and this line in /etc/exports:

   /export/home	physics

   So, for example, the host color.phys.psu.edu, should be able to mount
   /export/home, right?  I get permission denied.  If I put color.phys.psu.edu
   in the export line, it works.  Major blah.  This doesn't work on our ultrix
   4.0 and our ultrix 4.3 system.

What I have had to do to get netgroups to work in a heterogenous system is make
a netgroup for each host consisting of the unqualified and fully qualified
host name. This is because different versions of NFS get the host names 
different ways.  What has worked for us for several years over a couple of
hundred systems from a wide variety of vendors and operating systems, 
including various versions of hp-ux and ultrix is something like this:

In /etc/netgroup:
ash (ash,-,nis.ece) (ash.ece.ucdavis.edu,-,nis.ece)
elm (elm,-,nis.ece) (elm.ece.ucdavis.edu,-,nis.ece)

trees	ash elm

You can then use trees in /etc/exports.

/etc/netgroup is actually generated from a script that uses a
set of host and user lists controlled by various lab managers. nis.ece is
the name of the nis domain.  It is listed explicitly, along with the '-'
because otherwise a rather small number of entries will break some size
limit that makedbm imposes (I think. It's been a while since I put this
stuff together).  Anyway, my job would be immensely more complicated if
netgroups did not work, thank goodness they do.

Tom Arons			Internet: arons@ece.ucdavis.edu
ECE Department
University of California
Davis, CA 95616			Phone:    (916) 752-1750

 Tom