Date: Sat, 20 Sep 1997 16:44:51 +0930 From: Greg Lehey <grog@lemis.com> To: dk+@ua.net Cc: freebsd-hackers@freebsd.org Subject: Re: nfs startup Message-ID: <19970920164451.27669@lemis.com> In-Reply-To: <199709200619.XAA00534@dog.farm.org>; from Dmitry Kohmanyuk on Fri, Sep 19, 1997 at 11:19:50PM -0700 References: <199709200619.XAA00534@dog.farm.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Sep 19, 1997 at 11:19:50PM -0700, Dmitry Kohmanyuk wrote: > 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? No, but if he's running that way, he shouldn't have any problems. > OTOH, imagine system which NFS mounts /usr . (named is in /usr ) You're unlikely to run named on what is effectively a diskless workstation. Greg
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19970920164451.27669>