Date: Fri, 19 Sep 1997 23:19:50 -0700 (PDT) From: Dmitry Kohmanyuk <dk@dog.farm.org> To: grog@lemis.com (Greg Lehey) Cc: freebsd-hackers@freebsd.org Subject: Re: nfs startup Message-ID: <199709200619.XAA00534@dog.farm.org>
next in thread | raw e-mail | index | archive | help
In article <19970916105940.15713@lemis.com> you wrote: > On Thu, Sep 04, 1997 at 11:31:48PM +0100, Brian Somers wrote: > > This has to be a dumb question, but I can't fathom it. > > > > /etc/rc sources /etc/rc.network and then runs network_pass1. > > Directly afterwards, it runs ``mount -a -t nfs''. > > > > However, network_pass3 (invoked much later) starts nfsiod along with > > the other nfs stuff. > You don't need nfsiod for mounting, but you do need to resolve the > names. If you're running a name server, I don't think it's reasonable > to expect an /etc/hosts entry for each system you're mounting NFS file > systems from. Unfortunately, named doesn't get started until > network_pass2, so this can't work in a name server environment. You mean that you expect somebody to run named and have this named at the _only_ nameserver available and making this machine NFS client? I don't see this situation as very typical... If there is other name servers on the network, list them in /etc/resolv.conf (and if the network with lots of NFS servers has only one name server, this is much more dangerous situation). OTOH, imagine system which NFS mounts /usr . (named is in /usr ) -- "- Why are we hiding from the police dad? - They use EMACS son. We use vi." --- Peter Gutmann
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199709200619.XAA00534>