Date: Mon, 4 Mar 2002 09:20:02 +0000 From: Ceri <setantae@submonkey.net> To: Tom Rhodes <darklogik@pittgoth.com> Cc: freebsd-doc@freebsd.org Subject: Re: docs/35098: [PATCH] Handbook NFS stuff Message-ID: <20020304092002.GA2321@submonkey.net> In-Reply-To: <200203040710.g247A1Y75400@freefall.freebsd.org> References: <200203040710.g247A1Y75400@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Mar 03, 2002 at 11:10:01PM -0800, Tom Rhodes wrote: Ok, I'm late in the game, but I have some changes that aren't just cosmetic that I'd like to see made. Sorry Tom ;) > + <firstname>Tom</firstname> > + <surname>Rhodes</surname> > + <contrib>Reorganized and enhanced by </contrib> > + </author> > + </authorgroup> > + <authorgroup> > + <author> Should there be multiple <authorgroup> elements ? (I don't know, I'm asking). > + <para><acronym>NFS</acronym> consists of at least two main parts: a server > + and at least one client. I don't like this - "at least" occurs at least once too often, imho. > + <application>nfsiod</application>. The <application>nfsiod</application> > + daemon services the requests from the <acronym>NFS</acronym> server. This > + is optional, and improves performance, but is not required for normal > + and correct operation. See the &man.nfsiod.8; manual page for more information. I've read the manual page, and I'm not really any the wiser here. nfsiod services async requests according to the manpage - what if i don't have any filesystems mounted async ? Is this the same thing as biod on Solaris ? While this may not be the best place to answer such questions, they're questions that I have after reading this chapter, and they aren't answered anywhere else. > + <para><acronym>NFS</acronym> configuration is relatively straightforward > + process. The processes that need to be running can all start at boot time with ... a relatively... ^^^ > + information. The <option>-alldirs</option> flag allows the directories > + below the specified filesystem to also be exported.</para> Um, no it doesn't. Not really. This reads as though failing to specify -alldirs will allow me to mount /home, but will not result in /home/setantae being exported. The -alldirs flag actually allows the directories below the specified filesystem to be used as the root of a mount point, i.e. using the line below will allow 10.0.0.[2-4] to mount /home/setantae from the server. Now try turning that into English :) > <programlisting>/home -alldirs 10.0.0.2 10.0.0.3 10.0.0.4</programlisting> > + <para>The following line exports <filename>/a</filename> so that two > + clients from different domains may access the filesystem. The > + <option>-maproot=0</option> flag allows the <username>root</username> I'd rather see -maproot=root here (and everywhere else). Although that may cause problems interoperating with Plan9, where the superuser appears to be called "glenda", it doesn't make it look as though something is being "turned off". > + Executing the following commands as <username>root</username>, > + should start everything up.</para> Kill that comma ? > + <note><para>The following <acronym>NFS</acronym> examples require > + <acronym>NFS</acronym> to be correctly configured before actual use, > + as previously discussed.</para> > + </note> Well, duh! Can we just kill this note ? > + <para>&man.amd.8; (the automatic mounter daemon) > + is a useful that automatically mounts a A useful what ? Ceri To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020304092002.GA2321>