Date: Fri, 20 Mar 2009 16:57:57 -0400 From: John Baldwin <jhb@freebsd.org> To: Rick Macklem <rmacklem@uoguelph.ca> 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 Message-ID: <200903201657.58470.jhb@freebsd.org> In-Reply-To: <Pine.GSO.4.63.0903201554070.25641@muncher.cs.uoguelph.ca> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200903201657.58470.jhb>