From owner-freebsd-doc Wed Feb 20 1: 6:21 2002 Delivered-To: freebsd-doc@freebsd.org Received: from relay3-gui.server.ntli.net (relay3-gui.server.ntli.net [194.168.4.200]) by hub.freebsd.org (Postfix) with ESMTP id 6532537B400 for ; Wed, 20 Feb 2002 01:06:01 -0800 (PST) Received: from pc4-card4-0-cust162.cdf.cable.ntl.com ([80.4.14.162] helo=rhadamanth.private.submonkey.net ident=mailnull) by relay3-gui.server.ntli.net with esmtp (Exim 3.03 #2) id 16dShJ-0005aS-00; Wed, 20 Feb 2002 09:05:57 +0000 Received: from setantae by rhadamanth.private.submonkey.net with local (Exim 3.34 #1) id 16dShI-0000j3-00; Wed, 20 Feb 2002 09:05:56 +0000 Date: Wed, 20 Feb 2002 09:05:56 +0000 From: Ceri To: Tom Rhodes Cc: freebsd-doc@freebsd.org Subject: Re: docs/35098: [PATCH] Handbook NFS stuff Message-ID: <20020220090556.GA2535@rhadamanth> Mail-Followup-To: Ceri , Tom Rhodes , freebsd-doc@freebsd.org References: <200202200350.g1K3o2D95303@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200202200350.g1K3o2D95303@freefall.freebsd.org> User-Agent: Mutt/1.3.27i Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tue, Feb 19, 2002 at 07:50:02PM -0800, Tom Rhodes wrote: > > Please review this, it has alot of your ideas, but a few of my own > tossed in here. I did cover more ground than listed, and have yet > to touch the amd part, well, more than the first paragraph hehe This is a large patch, so I am going to be as terse as possible with my comments; sorry to stick my oar in, if Michael and yourself would rather sort this out between yourselves that's cool too. > + the Network File System also known as NFS. ...System, also... OR ...System (NFS for short). > + NFS allows your system to share directories and files on > + with others over the network. That doesn't make sense. > + Some of the benefits for using NFS are: ..benefits of using.. > - How It Works > + How <acronym>NFS</acronym> Works Don't think we need acronym there ?? > + NFS consists of at least two parts; a client and > + a server. The client remotely accesses the data that is stored locally > + on the server machine. In order for this to function properly a few > + processes have to be configured and running: i) indentation is cack here; ii) the words remotely and locally here are potentially confusing. > - The NFS Daemon which services requests from NFS > - clients. > + The NFS daemon which serves requests from > + the NFS clients. I prefer the original "services requests" to "serves requests", which doesn't seem to make sense. > - The NFS Mount Daemon which actually carries out > + The NFS mount daemon which actually carries out > requests that &man.nfsd.8; passes on to it. I know this isn't your copy, but : "actually carries out requests" seems redundant, viz. The NFS mount daemon which actually carries out requests that nfsd passes on to it (as opposed to silently discarding them like all the other processes do). > + The portmapper daemon > + allows NFS clients to find out which port the > + NFS server is using. i) indentation is all cack again ii) s/find out/discover/ iii) {setantae@rhadamanth}-{~} $ portmapper portmapper: Command not found. Not a at all, then. > + The client can also run a daemon, known as > + nfsiod. The nfsiod > + daemon services the requests from a NFS server. This, > + is optional, and improves performance, but not really required for normal > + and correct operation. See the &man.nfsiod.8; man page for more information. ..performance, but is not... > - On the NFS server make sure you have: > + On the NFS server, make sure that the following options > + in the /etc/rc.conf file: Doesn't make sense. make sure that the following options are configured in the + mountd runs automatically whenever the > + NFS server is enabled. The and > + flags tell nfsd to I'm going to complain about indentation again... > - Like nfsd, the tells > + Like with nfsd, the tells > nfsiod to start 4 copies of itself. s/Like/As/ > + The NFS configuration requires that a file > + called /etc/exports exsists. The exports file > + specifies which file systems on your server will be exported > + or shared and with what clients they will > + exported too. Each line in the file specifies a file system to be > + exported. There are many options that can be used in this i) indentation, indentation, indentation ii) |ispell ? s/exsists/exists/ ? ii) I prefer this : NFS configuration requires that a file named /etc/exports exist. The exports file specifies which filesystems on the server will be shared (or exported), and with which clients. Each line in /etc/exports specifies a filesystem to be exported and the options with which this will be done. There are many such option that can be used in this... Assuming of course, that is valid in the Handbook. Otherwise, maybe . > - exporting filesystems > + examples of exporting filesystems I don't feel that's necessary in an . > + In the following examples, an idea of how to export filesystems > + is displayed, although the settings may be different depending on > + environment and network setup. If we're using "you/your" (as we are above), I'd prefer "..depending on your environment and..." here. > - /cdrom -ro moe larry curly > + /cdrom -ro example1 example2 example3 s/example/host/g ? > + private network but do not have a DNS server configured. The > + flag allows for all of the directories below > the specified file system to be exported as well. Don't think that both of "all of" and "as well" are necessary. > + The following line exports /a so that two > + machines with different domain names may access the server. The > + flag allows the root indentation :) > + user on the remote system to write data on the exported file system as > + root. Without the -maproot=0 flag, even if -maproot=0 isn't an option anymore ? > + someone has root access on the remote system they will not > + be able to modify files on the exported file system. > > - /a -maproot=0 host.domain.com box.example.com > + /a -maproot=0 host.example.com box.example2.com example2.com isn't a documentation friendly domain. example.org instead ? > - In /etc/exports, each line represents > + In the /etc/exports file, each line represents > the export information for one filesystem to one host. A > - remote host can only be specified once for each local > - filesystem, and you can only have one default entry per local > + remote host can only be specified once per > + filesystem, and may only have one default entry for each > filesystem. For example, let's assume that > /usr is a single filesystem. The > - following /etc/exports is invalid: > + following /etc/exports would be invalid: I've been responsible for some rather spectacular NFS abortions in my time, and I still don't understand the above paragraph. What's a default entry ? I don't like from here until the end of the section at all : > - You must restart > - mountd whenever you modify > - /etc/exports to make changes take > - effect. This can be accomplished by sending the hangup signal > + You must restart mountd whenever you modify > + /etc/exports to make the changes current. > + This can be accomplished by either sending the hangup signal The "or" that goes with this "either" is too far away. > + Or, a simple reboot should make FreeBSD set everything up > + for you. Although, a reboot is not nessissary > + the following commands, run as root of course, > + could start everything up also. i) s/nessissary/necessary/ ii) It doesn't scan at all. iii) A reboot _will_ work, if everything is set up correctly. > name will be client. If you just want to > - temporarily mount a remote file system or just want to test out > - your configuration you can run a command like this as root on the > + temporarily mount a remote file system or just want to test the > + configuration, just run a command like this as root on the > client: That sentence contains the word "just" at least three times. Just use "just" just once ;) > This will mount the /home directory > on the server at /mnt on the client. If > - everything is setup correctly you should be able to go into > - /mnt on the client and see all the files that are on the > + everything is setup correctly you should be able to enter I'll get in here before Gary does ;) s/setup/set up/ > If you want to automatically mount a remote file system > + The &man.fstab.5; manual page will show many more options that are available. > The &man.fstab.5; manual page lists all available options. > + There are many practical uses for NFS. Some of the > + more common ones are listed below: > + > + The following practicle NFS examples require You already said they were practical. s/practicle// > + the proper NFS configuration before actual use. NFS to be correctly configured... > - Have several machines on a network and share a CDROM or > - floppy drive among them. This is cheaper and often more > - convenient. > + Setup several machines on a network to share a CDROM or > + floppy drive among them. This is cheaper and often more convenient. s/Setup/Set up/ > - With so many machines on a network, it gets old having your > - personal files strewn all over the place. You can have a > - central NFS server that houses all user home directories and > - shares them with the rest of the machines on the LAN, so no > - matter where you log in you will have the same home > - directory. > + With so many machines on a network, you can have a > + central NFS server store the user home directories and > + export them with the rest of the machines on the network, this way > + users can have the same home directory, regardless of which workstation > + they log in to. With how many machines ? And it won't work if I've got N-1 machines ? (picky in the extreme, I know) > - &man.amd.8;, which is also known as the automatic mounter > + &man.amd.8;, also known as the automatic mounter &man.amd.8; (the automatic mounter daemon) ... > - to static mounts. > + to perminant mounts. eh ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message