From owner-freebsd-current Sun Apr 20 12:17:22 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA07190 for current-outgoing; Sun, 20 Apr 1997 12:17:22 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA07184 for ; Sun, 20 Apr 1997 12:17:17 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.5/8.8.5) with ESMTP id MAA08006 for ; Sun, 20 Apr 1997 12:17:16 -0700 (PDT) Message-Id: <199704201917.MAA08006@austin.polstra.com> To: current@freebsd.org Subject: amd breakage in -current Date: Sun, 20 Apr 1997 12:17:14 -0700 From: John Polstra Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I don't have time to look into this right now, so I'll just report it. I'm using a system built from sources CVSupped around 17:00 PDT yesterday (April 19), with a full make world and kernel build. "amd" doesn't seem to work. When I try to chdir into an amd-managed directory, there are console messages like this: amd[237]: /net/austin/home: mount: Bad address The messages appear on the NFS client, and "austin" is the server. The server is a 2.2-stable system no more than a month old. On the client, I can manually mount the indicated directories. But "amd" can't do it. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth