Date: Tue, 05 Mar 2002 10:36:32 -0500 From: Tom Rhodes <darklogik@pittgoth.com> To: Ceri <setantae@submonkey.net> Cc: freebsd-doc@freebsd.org Subject: Re: docs/35098: [PATCH] Handbook NFS stuff Message-ID: <3C84E600.3030209@pittgoth.com> References: <200203040710.g247A1Y75400@freefall.freebsd.org> <20020304092002.GA2321@submonkey.net> <3C839B52.3020206@pittgoth.com> <20020305101859.GA4224@submonkey.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Ceri wrote: > On Mon, Mar 04, 2002 at 11:05:38AM -0500, Tom Rhodes wrote: > >>How does "a minimial of one client" sound to you? >> > > I'm with Giorgos - "one or more" is better. > After all, I'm not going to turn up on anyone's doorstep if they > dare to set up a server and no clients, so we shouldn't make it > sound as someone is going to ;) I'm not going to complain, the more I thought about it, the more logical it became in my mind, I will throw togeather another patch ;) > > >>>><application>nfsiod</application> >>>> >>>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 ? >>> >>Well would you want them? and I don't use Solaris, not for NFS anyways, >>so I would have no clue what your talking about it you even mentioned >>biod. If you want to reword that to help the Solaris boys please offer >>an opinion as I'm at a loss. >> > > It looks like it is (from the biod manpage on an arcane version of SunOS) : > > biod starts nservers asynchronous block I/O daemons. This > command is used on a NFS client to buffer cache handle > read-ahead and write-behind. > > Whether we want to start saying "foo is the equivalent of bar on QuuxOS" is > a question that will probably be answered in the negative - it was rather > frustrating, however, to be referred to the manpage and find nothing more > there, but that's not really your problem, I suppose; the manpage needs > fixing too. Maybe I should just remove the reference to the man page? Or just leave it in hopes that someone will eventually work on the manual page? > >>>>+ 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 :) >>> >>I am trying to think of a better example, this one made me think for a >>few moments ;) But the ``vision'' is approching ;) > > OK, but you know what I'm saying, right ? This is how I read what you say: "I guess that using the -alldirs option will PERMIT the mounting of subdirectories, without requiring a seperate entry for them? In this way, you could export the /home dir, and not be required to specify which user home directories be exported..." > > >>>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". >>> >>I can agree with this, although about the Plan9 interoperation problem, >>that SHOULD be documented on their side. Most *nix versions use the >>root user ;) >> > > Wizard. > > Thanks, > > Ceri > > I hope this sounds better... Enjoy -- Tom (Darklogik) Rhodes www.Pittgoth.com Gothic Liberation Front www.FreeBSD.org The Power To Serve 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?3C84E600.3030209>