From owner-freebsd-questions  Tue Jul 22 10:19:52 1997
Return-Path: <owner-freebsd-questions>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id KAA12264
          for questions-outgoing; Tue, 22 Jul 1997 10:19:52 -0700 (PDT)
Received: from 280.com (postoffice.280.com [205.227.166.100])
          by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA12259
          for <freebsd-questions@freebsd.org>; Tue, 22 Jul 1997 10:19:50 -0700 (PDT)
Received: from set.280.com by 280.com (SMI-8.6/SMI-SVR4)
	id KAA27469; Tue, 22 Jul 1997 10:18:42 -0700
From: Dan Grillo <Dan_Grillo@280.com>
Message-Id: <199707221718.KAA27469@280.com>
Received: by set.280.com (SMI-8.6/SMI-SVR4)
	id KAA02543; Tue, 22 Jul 1997 10:15:23 -0700
Date: Tue, 22 Jul 1997 10:15:23 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Organization: 280, Inc.
To: freebsd-questions@freebsd.org
Subject: can't automount from NEXTSTEP 3.x server w/2.2.2, worked with 2.1.x
Versions: dmail (solaris) 2.1t/makemail 2.8o
Sender: owner-freebsd-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


I'm having problems with a machine that was recently upgraded
from FreeBSD 2.1.5 to 2.2.2.   Automounting from a NEXTSTEP 3.2 (4.3 BSD,
NFS version 2) NFS server broke:

# cd /Net/slack
/Net/slack: Protocol not supported.

This used to work with amd and earlier versions of FreeBSD.

I'm using the stock /etc/amd.map file, and running amd as:

amd -a /amd -c 1800 -k i386 -l syslog /Net /etc/amd.map


Mounting from machine slack manually works:

# mount slack:/ /mnt
# ls /mnt | wc -l
      35

Trying to debug this has run into problems:

# tcpdump -s 100 host slack
tcpdump: listening on ed0
10:24:39.707452 more.29fdf052 > slack.nfs: 96 access [|nfs]
Segmentation fault

Does anyone have ideas?

Thanks.

				--Dan
--
  Dan Grillo  dan_grillo@280.com  415 575-4020   fax 415 703-7220