From owner-freebsd-arch@FreeBSD.ORG  Fri Mar 20 21:38:17 2009
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
Delivered-To: freebsd-arch@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id E5D90106564A;
	Fri, 20 Mar 2009 21:38:17 +0000 (UTC) (envelope-from jhb@freebsd.org)
Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42])
	by mx1.freebsd.org (Postfix) with ESMTP id B4DA78FC18;
	Fri, 20 Mar 2009 21:38:17 +0000 (UTC) (envelope-from jhb@freebsd.org)
Received: from server.baldwin.cx (pool-98-109-39-197.nwrknj.fios.verizon.net
	[98.109.39.197])
	by cyrus.watson.org (Postfix) with ESMTPSA id 49DCA46B65;
	Fri, 20 Mar 2009 17:38:17 -0400 (EDT)
Received: from localhost (john@localhost [127.0.0.1]) (authenticated bits=0)
	by server.baldwin.cx (8.14.3/8.14.3) with ESMTP id n2KLcBFn029100;
	Fri, 20 Mar 2009 17:38:11 -0400 (EDT) (envelope-from jhb@freebsd.org)
From: John Baldwin <jhb@freebsd.org>
To: Rick Macklem <rmacklem@uoguelph.ca>
Date: Fri, 20 Mar 2009 16:57:57 -0400
User-Agent: KMail/1.9.7
References: <Pine.GSO.4.63.0903151520590.16993@muncher.cs.uoguelph.ca>
	<200903201538.45268.jhb@freebsd.org>
	<Pine.GSO.4.63.0903201554070.25641@muncher.cs.uoguelph.ca>
In-Reply-To: <Pine.GSO.4.63.0903201554070.25641@muncher.cs.uoguelph.ca>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200903201657.58470.jhb@freebsd.org>
X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by
	milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]);
	Fri, 20 Mar 2009 17:38:11 -0400 (EDT)
X-Virus-Scanned: ClamAV 0.94.2/9145/Fri Mar 20 10:59:16 2009 on
	server.baldwin.cx
X-Virus-Status: Clean
X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 
	autolearn=ham version=3.1.3
X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx
Cc: Zachary Loafman <zachary.loafman@isilon.com>,
	Alfred Perlstein <alfred@freebsd.org>, freebsd-arch@freebsd.org
Subject: Re: NFS version 4.0 for FreeBSD-CURRENT
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussion related to FreeBSD architecture <freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Mar 2009 21:38:18 -0000

On Friday 20 March 2009 4:00:38 pm Rick Macklem wrote:
> 
> On Fri, 20 Mar 2009, John Baldwin wrote:
> 
> >
> > FreeBSD in general is moving away from new flags in mnt_flags I believe.  
At
> > least if you purely need NFS-specific flags you can just add new string
> > options via nmount(2) and set appropriate settings in private flags field 
in
> > your NFS-specific mount data.
> >
> Ok, thanks. I vaguely knew about nmount(2), but didn't realize it was
> being used for server exports. (The MNT_EXxxx flags are/were used by the 
> NFS server and are relevant when set on an exported local fs like UFS/FFS.
> As such, they are either generic mount stuff or UFS/FFS specific. I
> think ZFS keeps its own export stuff, so making it UFS/FFS specific
> might make sense?)
> 
> Anyhow, it's not urgent, since the server works ok without any additional
> flags.

Ahhh, ok, that is different then.  I must have misunderstood.  If it is flags 
the NFS server sets on arbitrary filesystems to manage exporting then 
a 'mnt_exflags' field might be best.

-- 
John Baldwin