Path: utzoo!utgpu!watmath!clyde!att!rutgers!mailrus!cornell!uw-beaver!rice!sun-spots-request
From: krempel@pacrat.npac.syr.edu (Henry B.J. Krempel)
Newsgroups: comp.sys.sun
Subject: SunSpots Automount query
Message-ID: <8811221619.AA01905@sixpac.npac.syr.edu>
Date: 2 Dec 88 21:32:38 GMT
Sender: usenet@rice.edu
Organization: Rice University, Houston, Texas
Lines: 38
Approved: Sun-Spots@rice.edu
Original-Date: Tue, 22 Nov 88 11:19:34 -0500
X-Sun-Spots-Digest: Volume 7, Issue 33, message 8 of 12

I have used automount quite a bit,  and it works fine,  except for some
circumstances.

I use it this way:

automount -m /net -hosts /vol auto.vol

(these are default names for examples in the manual,  and on the 386i, I
have to admit that I didn't understand automount fully until I looked at
the 386i setup).

The /net entry allows me to refer to disks on other systems:

cd /net/rodan/u1/

puts me at rodan:/u1

the other entry comes from a yp map "auto.vol"  which maps sofytware
package names to their location on the net.  /etc/auto.vol looks like
this: 

maker: 		sparky:/usr/maker
emacslib:	pacrat:/usr/local/lib/emacs
diamond:	sparky:/usr/diamond
Art:		sparky:/usr/Art

when /vol/Art is referred to,  the appropriate file is automounted.

NOTE: I have had a few problems:

When you have something in your current working directory that is resident
on a machine that is down, it may lock up that session.  This happenned to
me with a file in my home directory,  suntools froze.  So putting cute
links like:  ln -s /net/cmx/u1/g1/me cmx in your home directory is
ill-advised.

I would not use automount extensively on a machine that you were doing
research demos on.