Added subsection about AMD to the NFS section.

Submitted by:	Wylie Stilwell <wylie@beerho.com>
Approved by:	murray

en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml

@@ -1,7 +1,7 @@
 <!--
      The FreeBSD Documentation Project
 
-     $FreeBSD: doc/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml,v 1.74 2001/08/09 22:50:09 logo Exp $
+     $FreeBSD: doc/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml,v 1.75 2001/08/09 23:42:29 chern Exp $
 -->
 
 <chapter id="advanced-networking">
@@ -798,6 +798,66 @@ nfs_client_flags="-n 4"</programlisting>
       </itemizedlist>
     </sect2>
 
+    <sect2 id="amd">
+      <sect2info>
+	<authorgroup>
+	  <author>
+	    <firstname>Wylie</firstname>
+	    <surname>Stilwell</surname>
+	    <contrib>Contributed by </contrib>
+	  </author>
+	</authorgroup>
+      </sect2info>
+      <title>AMD (automatic mounter daemon)</title>
+
+      <indexterm><primary>AMD</primary></indexterm>
+      <indexterm><primary>automatic mounter daemon</primary></indexterm>
+
+      <para>AMD is a usefull utility used for automatically mounting a
+	filesystem whenever a file or directory within that filesystem is
+	accessed. It will also unmount that filesystem when it has not
+	been used for a time.</para>
+
+      <para>AMD operates by listening in the
+	<filename>/host</filename> and <filename>/net</filename>
+	directories for a filename lookup. On a lookup, it uses the
+	system's resolver routine to find the NFS server, and attempts
+	to map the exported filesystems on the NFS server to the
+	<filename>/host/${HOSTNAME}/</filename> directory.</para>
+
+      <para>The process actually goes a little something like
+	this:</para>
+
+      <itemizedlist>
+	<listitem><para>Someone cd's into
+	    <filename>/host/<varname>${HOSTNAME}</varname>/exported_filesystem</filename>.</para></listitem>
+
+	<listitem><para>AMD recieves the lookup request, and takes the
+	    <varname>${HOSTNAME}</varname> token.</para></listitem>
+
+	<listitem><para>AMD attempts to resolve the <varname>HOSTNAME</varname>
+	    token, and map any exports on the server into the
+	    <filename>/host/<varname>${HOSTNAME}</varname>/</filename> directory.</para></listitem>
+      </itemizedlist>
+
+      <para>Setting up amd is actually quite simple, perhaps deceptively
+	so:</para>
+
+      <para>Put <varname>amd_enable="YES"</varname> in the
+	<filename>rc.conf</filename> file of the client machine. Thats
+	it, everything you need is already installed. Reboot the machine
+	and amd will create a host directory in your root
+	partition. Then, you can access the remote filesystem like
+	this:</para>
+
+      <screen>&prompt.user;<userinput>cd /host/<replaceable>1.1.1.1</replaceable>/file/</userinput></screen>
+
+      <para>Also if you have DNS up and running, you can access the
+	filesystem like this:</para>
+
+      <screen>&prompt.user;<userinput>cd /host/<replaceable>machinename</replaceable>/file/</userinput></screen>
+    </sect2>
+
     <sect2>
       <sect2info>
         <authorgroup>
@@ -912,7 +972,7 @@ nfs_client_flags="-n 4"</programlisting>
 	and acknowledged.</para>
     </sect2>
   </sect1>
-  
+
   <sect1 id="diskless">
     <sect1info>
       <authorgroup>
@@ -1476,7 +1536,7 @@ ISDN BRI line</literallayout>
           <firstname>Bill</firstname>
       	  <surname>Swingle</surname>
 	  <contrib>Written by </contrib>
-	  </author>
+         </author>
       </authorgroup>
       <authorgroup>
 	<author>