From owner-freebsd-current@FreeBSD.ORG Mon Nov 16 16:15:30 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E265F106566B for ; Mon, 16 Nov 2009 16:15:30 +0000 (UTC) (envelope-from gerrit@pmp.uni-hannover.de) Received: from mrelay1.uni-hannover.de (mrelay1.uni-hannover.de [130.75.2.106]) by mx1.freebsd.org (Postfix) with ESMTP id 6BEF48FC22 for ; Mon, 16 Nov 2009 16:15:29 +0000 (UTC) Received: from www.pmp.uni-hannover.de (www.pmp.uni-hannover.de [130.75.117.2]) by mrelay1.uni-hannover.de (8.14.2/8.14.2) with ESMTP id nAGGFR0S014946; Mon, 16 Nov 2009 17:15:28 +0100 Received: from pmp.uni-hannover.de (theq.pmp.uni-hannover.de [130.75.117.4]) by www.pmp.uni-hannover.de (Postfix) with SMTP id 30AE924; Mon, 16 Nov 2009 17:15:27 +0100 (CET) Date: Mon, 16 Nov 2009 17:15:27 +0100 From: Gerrit =?ISO-8859-1?Q?K=FChn?= To: Rick Macklem Message-Id: <20091116171527.0b44bae8.gerrit@pmp.uni-hannover.de> In-Reply-To: References: <20091112182414.cebec1df.gerrit@pmp.uni-hannover.de> <20091113103626.414acdbc.gerrit@pmp.uni-hannover.de> <20091116112631.e8733905.gerrit@pmp.uni-hannover.de> Organization: Albert-Einstein-Institut (MPI =?ISO-8859-1?Q?f=FCr?= Gravitationsphysik & IGP =?ISO-8859-1?Q?Universit=E4t?= Hannover) X-Mailer: Sylpheed 2.4.2 (GTK+ 2.10.12; i386-portbld-freebsd6.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-PMX-Version: 5.5.5.374460, Antispam-Engine: 2.7.1.369594, Antispam-Data: 2009.11.16.160325 Cc: freebsd-current@freebsd.org Subject: Re: nfsv4 FreeBSD server vs. Linux client I/O error X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Nov 2009 16:15:31 -0000 On Mon, 16 Nov 2009 10:50:16 -0500 (EST) Rick Macklem wrote about Re: nfsv4 FreeBSD server vs. Linux client I/O error: RM> > P.S.: And one more question comes to my mind: How do I prevent a dir RM> > from being mountable with nfs3? With the extra exports line it will RM> > also be available as nfs3, won't it? RM> Yep, there is currently no way to say that an exported fs is for nfsv4 RM> only. There are sysctl's that can restrict what versions of nfs the RM> experimental server handles, but they apply to all mounts. RM> If a lot of people need this feature, I can look at adding it, but RM> my nfs todo list is getting pretty long and one of them is to look RM> at a possible mountd replacement. (This might be a part of that?) Not for me, I do not need the feature. I was only thinking about it because the better security of nfsv4 is easily gotten around when you allow for the old v3 mounts in parallel. RM> ps: I hope you didn't mind me adding freebsd-current@ as a cc, since RM> I figured others will need the info someday. Yes, of course. I also had the plan to cc: the list, but then forgot about it. Thanks for your support. cu Gerrit