I've been using amd on bleeding-edge current for the past year or so with no problems - the servers in my case are Solaris 2.5.1 boxes.
I remember becoming extremely confused when I configured my first amd map file, since there was no coherent documentation to be found at the time, but I ended up with this (and have kept it ever since): % grep amd /etc/rc.conf amd_enable="YES" # Run amd service with $amd_flags (or NO). amd_flags="-a /a -c 1800 -k i386 -d clear.net.nz -l syslog /home /etc/amd.home.map /net /etc/amd.net.map" amd_map_program="NO" # Can be set to "ypcat -k amd.master" % % cat /etc/amd.home.map # auto-mount home directories /defaults type:=nfs;rfs=/export/${path};rhost:=oms jabley rhost:=intdev * opts:=rw,resvport % % cat /etc/amd.net.map # automount /net hierarchies /defaults opts:=rw,grpid,resvport,nosuid buddha type:=link;fs=/ * type:=host;rhost:=${key} buddha is the local machine; intdev is where my home directory happens to be (everybody else's is mounted off oms). Never had a problem with it. Just to confirm that amd is not hideously broken beyond the point where _some_ people can use it just fine. Joe To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message