From owner-freebsd-stable Wed Feb 25 15:27:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA23837 for freebsd-stable-outgoing; Wed, 25 Feb 1998 15:27:13 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from xmission.xmission.com (softweyr@xmission.xmission.com [198.60.22.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA23700 for ; Wed, 25 Feb 1998 15:26:59 -0800 (PST) (envelope-from softweyr@xmission.xmission.com) Received: (from softweyr@localhost) by xmission.xmission.com (8.8.7/8.7.5) id QAA17514; Wed, 25 Feb 1998 16:26:43 -0700 (MST) From: Wes Peters - Softweyr LLC Message-Id: <199802252326.QAA17514@xmission.xmission.com> Subject: Re: 2.2.6 for NFS server To: jfieber@indiana.edu (John Fieber) Date: Wed, 25 Feb 1998 16:26:42 -0700 (MST) Cc: stable@FreeBSD.ORG In-Reply-To: from "John Fieber" at Feb 25, 98 05:17:55 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > Depends on your clients. For 2.2.5, I can confirm that Solaris > and Digital Unix clients do NOT work using nfs v3. Digital Unix > works fine if you specify v2 when mounting. Telling FreeBSD > mountd to only accept v2 does not seem to allow mounts from > Solaris clients using their automounter (I'm not the admin of the > Solaris boxes in question so I can't do much more investigation.) You can probably take care of this problem for the Solaris clients by specifying vers=2 in the mount options. > In other words: Try it out. Always a good suggestion. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.xmission.com/~softweyr softweyr@xmission.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message