From owner-freebsd-stable  Mon Jul 28 22:44:12 1997
Return-Path: <owner-freebsd-stable>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id WAA11911
          for stable-outgoing; Mon, 28 Jul 1997 22:44:12 -0700 (PDT)
Received: from set.sands.com (dal99.metronet.com [192.245.137.99])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA11855
          for <stable@freebsd.org>; Mon, 28 Jul 1997 22:43:58 -0700 (PDT)
Received: from set.sands.com (tsprad@localhost [127.0.0.1])
	by set.sands.com (8.8.5/8.8.5) with ESMTP id UAA02308
	for <stable@freebsd.org>; Mon, 28 Jul 1997 20:58:37 -0500 (CDT)
Message-Id: <199707290158.UAA02308@set.sands.com>
X-Mailer: exmh version 2.0gamma 1/27/96
To: stable@freebsd.org
Subject: Re: mount_msdos -- is it safe yet? 
In-reply-to: Your message of "Mon, 28 Jul 1997 09:06:47 +0200."
             <19970728090647.30861@btp1da.phy.uni-bayreuth.de> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 28 Jul 1997 20:58:36 -0500
From: Ted Spradley <tsprad@set.sands.com>
Sender: owner-freebsd-stable@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


werner@btp1da.phy.uni-bayreuth.de said:
> On Sun, Jul 27, 1997 at 05:25:22PM +0400, Seva Semenov wrote: [...]
> > Yes.. 
> > btw.. is it safe to mount_nfs in 2.2.2-RELEASE?
> > I was waiting for some1 who report it, but it seems 
> > like this only my problem. [...]
> 
> Use option "nfsv2" to make it work, unfortunately nfsv3 is the
> default.
> Werner
> 

Could this be the cause of my difficulty with amd in 2.2.2-RELEASE?  With 
2.2.1 and previous versions the example /etc/amd.map worked fine with AIX 
3.2.5 and DEC OSF/1 servers, with 2.2.2 I get 'Permission denied' messages.  I 
can mount the same filesystems from the command line with no special arguments.

Does anyone know the magic to get amd to use these options?  I never have 
figured out how to get amd to use the -P option to mount a Linux filesystem, 
so I have to put it in fstab and keep it mounted all the time.