Xref: utzoo comp.sys.apollo:7086 comp.unix.admin:518
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!uunet!ogicse!orstcs!prism!larsen
From: larsen@prism.cs.orst.edu (Scott Larsen)
Newsgroups: comp.sys.apollo,comp.unix.admin
Subject: Re: NFS Mount Point Strategy?
Summary: /nfs/machinename/partitionname
Message-ID: <21753@orstcs.CS.ORST.EDU>
Date: 14 Nov 90 01:23:32 GMT
References: <1990Nov10.144551.809@alchemy.chem.utoronto.ca>
Sender: usenet@orstcs.CS.ORST.EDU
Reply-To: larsen@prism.CS.ORST.EDU (Scott Larsen)
Organization: Oregon State Univ. -- Computer Science
Lines: 26

In article <1990Nov10.144551.809@alchemy.chem.utoronto.ca> system@alchemy.chem.utoronto.ca (System Admin (Mike Peterson)) writes:
>We have just got NFS working between our Apollo systems and SGI/IBM boxes,
>and I have a few questions about the "right" way to set things up:
.
.
>2) What directory structure is best for the actual mount points:

Well, here at OSU, all of our machines run NFS and we ran into a BIG
problem with inconsistant naming, so we thought a bit and cam up with
this:

mount all partitions under /nfs/machinename/partition.

This boils down to this:

a machine called prism with a /local would be /nfs/prism/local
a machine called mist with a /src would be /nfs/mist/src
a machine called jasper with a /usr/local/src would be 
	/nfs/jasper/usr-local-src with links pu in for /nfs/jasper/src
	and /nfs/jasper/usr/local/src

So far we have had no problems with this naming scheme.  We have been
using it for about 9 months now.

Scott Larsen
larsen@prism.cs.orst.edu