Path: utzoo!attcan!uunet!husc6!bloom-beacon!tut.cis.ohio-state.edu!rutgers!columbia!douglass!dupuy
From: dupuy@douglass.columbia.edu (Alexander Dupuy)
Newsgroups: comp.protocols.nfs
Subject: Re: Problems with PC-NFS
Message-ID: <5962@columbia.edu>
Date: 24 Oct 88 20:22:10 GMT
References: <1747@bu-tyng.bu.edu> <31289@bbn.COM>
Sender: news@columbia.edu
Reply-To: dupuy@douglass.columbia.edu (Alexander Dupuy)
Followup-To: comp.protocols.nfs
Organization: Columbia University Computer Science Dept.
Lines: 21

One technique I have found useful in dealing with fully qualified vs.
unqualified hostnames is to do the following in /etc/netgroup:

a-real-group	onemachine anothermachine thirdmachine

onemachine	(onemachine,,) (onemachine.dom.ain,,)
anothermachine	(anothermachine,,) (anothermachine.dom.ain,,)
thirdmachine	(thirdmachine,,) (thirdmachine.dom.ain,,)

This way you can define your netgroups by machines, not umpteen aliases, but
still accept both fully qualified and unqualified hostnames.  We have a mix of
Suns and Vaxen running 4.3+NFS, some of which use qualified, and some of which
don't - this system deals with them all.  This also helps with problems where
the "canonical" hostname (first one in /etc/hosts, or returned by ypmatch)
varies, depending on whether or not the domain nameserver is running (and
whether it's returning capitalized entries or not).

@alex
-- 
inet: dupuy@columbia.edu
uucp: ...!rutgers!columbia!dupuy