From owner-freebsd-fs@FreeBSD.ORG Mon Jul 11 21:09:25 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 90E2B106564A for ; Mon, 11 Jul 2011 21:09:25 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-annu.mail.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id 5460E8FC1F for ; Mon, 11 Jul 2011 21:09:24 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ap4EAFVmG06DaFvO/2dsb2JhbABTG4Qpo1ipaY4/kHaBK4QAgQ8EklaQYw X-IronPort-AV: E=Sophos;i="4.65,517,1304308800"; d="scan'208";a="126872217" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-annu-pri.mail.uoguelph.ca with ESMTP; 11 Jul 2011 17:09:16 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id C2F28B3FE3 for ; Mon, 11 Jul 2011 17:09:16 -0400 (EDT) Date: Mon, 11 Jul 2011 17:09:16 -0400 (EDT) From: Rick Macklem To: FreeBSD FS Message-ID: <10589627.445480.1310418556785.JavaMail.root@erie.cs.uoguelph.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.203] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - FF3.0 (Win)/6.0.10_GA_2692) Subject: request for review of exports.5 update X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jul 2011 21:09:25 -0000 Hi, I've added a few sentences to the exports.5 man page in an effort to try and clarify how NFSv4 exports work. If anyone would like to comment on these changes, it would be appreciated. Ideally, you are familiar with the FreeBSD /etc/exports file, but not w.r.t. NFSv4. The diff is at: http://people.freebsd.org/~rmacklem/exports.5.diff in case you can't handle looking at the following. (The email system I use loves to mess with whitespace, etc.) Index: usr.sbin/mountd/exports.5 =================================================================== --- usr.sbin/mountd/exports.5 (revision 223937) +++ usr.sbin/mountd/exports.5 (working copy) @@ -28,7 +28,7 @@ .\" @(#)exports.5 8.3 (Berkeley) 3/29/95 .\" $FreeBSD$ .\" -.Dd December 3, 2009 +.Dd July 11, 2011 .Dt EXPORTS 5 .Os .Sh NAME @@ -72,6 +72,12 @@ There are three forms of this specification. The first is to list all mount points as absolute directory paths separated by whitespace. +This list of directory paths should be considered an +``administrative control'', since it only enforced by the +.Xr mountd 8 +daemon and not the kernel. +As such, it only applies to NFSv2, NFSv3 mounts and only w.r.t. the +client's use of the mount protocol. The second is to specify the pathname of the root of the file system followed by the .Fl alldirs @@ -81,8 +87,19 @@ .Fl r option is used on .Xr mountd 8 . +For NFSv4, since the ``administrative controls'' are not applied +because NFSv4 does not use the mount protocol, +all of the above export line(s) should be considered to have the +.Fl alldirs +flag, even if the line is specified without it. The third form has the string ``V4:'' followed by a single absolute path name, to specify the NFSv4 tree root. +This line does not export any file system, but simply marks where the root +of the server's directory tree is for NFSv4 clients. +The exported file systems for NFSv4 are specified via the other lines +in the +.Xr exports 5 +file in the same way as for NFSv2, NFSv3. The pathnames must not have any symbolic links in them and should not have any .Dq Pa \&.