Date: Tue, 27 Oct 2009 22:39:29 +0100 From: "Arno J. Klaassen" <arno@heho.snv.jussieu.fr> To: "Larry Rosenman" <ler@lerctr.org> Cc: freebsd-net@freebsd.org Subject: Re: ZFS and 'traditional' nfs-export Message-ID: <wpmy3cikj2.fsf@heho.snv.jussieu.fr> In-Reply-To: <00b301ca5739$8e9b3850$abd1a8f0$@org> (Larry Rosenman's message of "Tue\, 27 Oct 2009 14\:13\:14 -0500") References: <wpbpjtwwg7.fsf@heho.snv.jussieu.fr> <00b301ca5739$8e9b3850$abd1a8f0$@org>
next in thread | previous in thread | raw e-mail | index | archive | help
hello, "Larry Rosenman" <ler@lerctr.org> writes: > ZFS makes its own version of the exports file. > > Just do it that way, and be safe. > > You can pass the full set of NFS options in the sharenfs parameter.... ah ok, I see. Thanks for answering. I got fooled by the man zfs(1M) example : zfs set sharenfs='rw=@123.123.0.0/16,root=neo' tank/home This syntax does not seem to work for me (8.0RC2). Maybe an extra line could be added that one can just set the sharenfs property to exactly the same character string as in /etc/exports. Once again, merci. Arno
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?wpmy3cikj2.fsf>