From owner-freebsd-current Sun Jan 31 04:17:42 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA21925 for freebsd-current-outgoing; Sun, 31 Jan 1999 04:17:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA21920 for ; Sun, 31 Jan 1999 04:17:41 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.2/8.9.2) with ESMTP id EAA01376; Sun, 31 Jan 1999 04:18:25 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: obrien@NUXI.com cc: current@FreeBSD.ORG Subject: Re: Even more interesting NFS problems.. In-reply-to: Your message of "Sun, 31 Jan 1999 02:49:14 PST." <19990131024914.C67786@relay.nuxi.com> Date: Sun, 31 Jan 1999 04:18:25 -0800 Message-ID: <1374.917785105@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Why is it clearly broken? proto=tcp,vers=3 is what is in 3.0-RELEASE, > Amd in 3.0 works for many. I won't defend that the new Amd works the > best with us, but then neither did the old Amd. Erm, I haven't tried it between 3.0 and 3.0 boxes because all my test environments currently involve one of each (4.0 and 3.0), but I can certainly say that in none of these test environments does amd work at all. On freefall, for example, it's really simple to demonstrate the error. First, we start amd: # amd -a /net -c 1800 -k i386 -d freebsd.org -l syslog /host /etc/amd.map # ps ax | grep amd 9127 ?? Is 0:00.01 amd -a /net -c 1800 -k i386 -d freebsd.org -l syslog # cat /etc/amd.map /defaults type:=host;fs:=${autodir}/${rhost};rhost:=${key} * opts:=rw,grpid,resvport,vers=2,proto=udp,nosuid,nodev,intr # df .. pid9127@freefall:/host 0 0 0 100% /host # ls /host/hub ls: /host/hub: No such file or directory # ls /host/bento ls: /host/bento: No such file or directory But no workee at all. Any ideas? Using only FreeBSD boxes and udp/ver2 mounts, amd fails to function as far as I can tell. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message