From owner-freebsd-doc Sat Dec 16 18:33:41 2000 From owner-freebsd-doc@FreeBSD.ORG Sat Dec 16 18:33:38 2000 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from bazooka.unixfreak.org (bazooka.unixfreak.org [63.198.170.138]) by hub.freebsd.org (Postfix) with ESMTP id BECB837B400 for ; Sat, 16 Dec 2000 18:33:37 -0800 (PST) Received: by bazooka.unixfreak.org (Postfix, from userid 1000) id 7742C3E09; Sat, 16 Dec 2000 18:33:37 -0800 (PST) Received: from bazooka.unixfreak.org (localhost [127.0.0.1]) by bazooka.unixfreak.org (Postfix) with ESMTP id 709B53C109; Sat, 16 Dec 2000 18:33:37 -0800 (PST) To: cjclark@alum.mit.edu Cc: doc@freebsd.org Subject: Re: NFS FAQ Entry In-Reply-To: Message from "Crist J. Clark" of "Sat, 16 Dec 2000 16:53:05 PST." <20001216165305.A88791@rfx-64-6-211-149.users.reflexco> Date: Sat, 16 Dec 2000 18:33:32 -0800 From: Dima Dorfman Message-Id: <20001217023337.7742C3E09@bazooka.unixfreak.org> Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I recently answered an NFS question on the -questions list that I have > responded to what seems like about, oh, 50 times, in the last two > years. Someone suggested a FAQ entry might be in order. I don't > have the doc sources, but here is a plain-text stab at an entry. I > think it would fit well in with FAQ items, 9.10, 9.11, and 9.12. > > > It's kind of long, and I have no problem adding more. > > Anyone think this is worth a FAQ entry? Been a while since I followed I do. In fact, I even took the time to mark it up! You can find the patch against book.sgml at the bottom of the message, and the preview of the rendered output at http://www.unixfreak.org/~dima/home/freebsd/data/FAQ/networking.html#EXPORTS-ERRORS > -doc, this is the right place to discuss this? What do I need to do to > get it added? Anyone have an opinion of whether it is worth including? Submitting a PR with the marked up version (see below) should speed up the commit process. And now, without further ado, here's the patch. The only modifications I made were to add the SGML markup, and to move around a few words to make it look a little better in a web browser. Regards -- Dima Dorfman Finger dima@unixfreak.org for PGP public key. Index: book.sgml =================================================================== RCS file: /st/src/FreeBSD/doc/en_US.ISO_8859-1/books/faq/book.sgml,v retrieving revision 1.129 diff -u -r1.129 book.sgml --- book.sgml 2000/12/05 13:18:16 1.129 +++ book.sgml 2000/12/17 02:20:16 @@ -7701,6 +7701,66 @@ + + Why does mountd keep telling me it + can't change attributes and that I have a + bad exports list on my FreeBSD NFS + server? + + + + The most frequent problem is not understanding this + passage from the &man.exports.5 manual page + correctly: + + Each line in the file (other than comment lines that begin with a #) +specifies the mount point(s) and export flags within one local server +filesystem for one or more hosts. A host may be specified only once +for each local filesystem on the server and there may be only one +default entry for each server filesystem that applies to all other +hosts. + + This is made more clear by an example of a common + mistake. If everything above /usr is + part of one filesystem (there are no mounts above + /usr) the following exports list is + not valid: + + /usr/src client +/usr/ports client + + There are two lines specifying properties for one + filesystem, /usr, exported to the + same host, client. The correct format + is: + + /usr/src /usr/ports client + + To rephrase the passage from the manual page, the + properties of one filesystem exported to a given host + (world-wide exports are treated like another unique host) + must all occur on one line. And yes, this does cause + limitiation in how you can export filesystems without ugly + workarounds, but for most people, this is not an + issue. + + The following is an example of a valid export list, + where /usr and + /exports are local + filesystems: + + # Export src and ports to client01 and client02, but only +# client01 has root privileges on it +/usr/src /usr/ports -maproot=0 client01 +/usr/src /usr/ports client02 +# The "client" machines have root and can mount anywhere +# up /exports. The world can mount /exports/obj read-only +/exports -alldirs -maproot=0 client01 client02 +/exports/obj -ro + + + + I'm having problems talking PPP to NeXTStep machines. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message