Date: Fri, 20 Mar 2009 16:00:38 -0400 (EDT) From: Rick Macklem <rmacklem@uoguelph.ca> To: John Baldwin <jhb@freebsd.org> 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: <Pine.GSO.4.63.0903201554070.25641@muncher.cs.uoguelph.ca> In-Reply-To: <200903201538.45268.jhb@freebsd.org> References: <Pine.GSO.4.63.0903151520590.16993@muncher.cs.uoguelph.ca> <20090319164251.GA13081@zloafman.west.isilon.com> <Pine.GSO.4.63.0903201149590.23530@muncher.cs.uoguelph.ca> <200903201538.45268.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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. rick
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.63.0903201554070.25641>