From owner-freebsd-current  Fri Jan 31 09:26:29 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id JAA02230
          for current-outgoing; Fri, 31 Jan 1997 09:26:29 -0800 (PST)
Received: from bach.ca.sandia.gov (bach.ca.sandia.gov [146.246.245.201])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA02224
          for <current@freebsd.org>; Fri, 31 Jan 1997 09:26:28 -0800 (PST)
Received: from bach.ca.sandia.gov (localhost [127.0.0.1])
	by bach.ca.sandia.gov (8.8.5/8.8.5) with ESMTP id JAA08833;
	Fri, 31 Jan 1997 09:22:58 -0800 (PST)
Message-Id: <199701311722.JAA08833@bach.ca.sandia.gov>
X-Mailer: exmh version 2.0gamma 1/27/96
To: Poul-Henning Kamp <phk@critter.dk.tfs.com>
cc: "Justin T. Gibbs" <gibbs@narnia.plutotech.com>, current@freebsd.org
Subject: Re: amd.map file format documentation 
In-reply-to: Your message of "Fri, 31 Jan 1997 08:43:23 +0100."
             <18753.854696603@critter.dk.tfs.com> 
From: bmah@CA.Sandia.GOV (Bruce A. Mah)
Reply-to: bmah@CA.Sandia.GOV
X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5<Pi&akO)o^8;[r
 %l(8ZHlbF`dD>v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A
 2V%N&+
X-Url: http://www.ca.sandia.gov/~bmah/
Mime-Version: 1.0
Content-Type: multipart/mixed ;
	boundary="==_Exmh_-13872276040"
Date: Fri, 31 Jan 1997 09:22:58 -0800
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

This is a multipart MIME message.

--==_Exmh_-13872276040
Content-Type: text/plain; charset=us-ascii

Poul-Henning Kamp writes:

> we really need a couple of good examples too.

I don't know if this counts as a "good" example, but I'm willing to throw up a 
strawman example.  This is one I used when I sysadminned some machines in grad 
school at Berkeley.  We'd often need to mount filesystems from servers (or 
workstations?) without necessarily knowing in advance what the servers or 
remote filesystems would be.

I set amd to start up in rc.local (or the equivalent on whatever the local OS 
was):

/usr/local/etc/amd -n -l syslog -d cs.berkeley.edu -x \
	all,nomap,nostats,nowarn,noinfo -a /tmp_mnt /n /usr/local/etc/amd.map

A few options of note:

"-a /tmp_mnt" set the mount point for NFS-mounted filesystems.

"/n /usr/local/etc/amd.map" meant the users would use /n as the top level 
directory to access the remote filesystems, configured using 
/usr/local/etc/amd.map.

The map (or rather the meaningful subset of it) is attached below.  Note that 
a few Berkeley-isms crept in, mostly because I didn't know how much of the 
FQDN for a server a user would supply in the pathname.

End result:  You could cd to /n/server and amd would mount all of the 
directories exported by server (subject to permissions) at /n/server/dir1 and 
/n/server/dir2.  The hitch was that if you had a server that exported (let's 
say) /usr/local and /usr/local/share, amd would put them on the client at 
/n/server/local and /n/server/share.

Bryan Costales (the sendmail book guy) set this up for me originally, I ended 
up tweaking it some afterwards.

Hope this is helpful to someone...

Cheers,

Bruce.



--==_Exmh_-13872276040
Content-Type: application/octet-stream ; name="amd.map"
Content-Description: amd.map
Content-Disposition: attachment; filename="amd.map"

#
# AMD automount map
#
/defaults       fs:=${autodir}${path};opts:=rw,intr,noquota,grpid

#
# servers are accessed via a -hosts style map
#
#*			type:=host;rhost:=${key};opts:=rw,intr,noquota,grpid,nosuid
*			key==${host};type:=link;fs:=/ \
			key==${key.}.cs;type:=link;fs:=${key.} \
			key==${key.}.CS;type:=link;fs:=${key.} \
			key==${key.}.cs.berkeley.edu;type:=link;fs:=${key.} \
			key==${key.}.CS.Berkeley.EDU;type:=link;fs:=${key.} \
			type:=host;rhost:=${key};fs:=${autodir}${path/}/${rhost};opts:=rw,intr,noquota,nosuid


--==_Exmh_-13872276040--