Date: Mon, 15 Sep 1997 21:21:21 +0100 From: Brian Somers <brian@awfulhak.org> To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Why not DNS (was: nfs startup - perhaps it is a problem) Message-ID: <199709152021.VAA07129@awfulhak.demon.co.uk> In-Reply-To: Your message of "Mon, 15 Sep 1997 08:44:37 %2B0200." <19970915084437.XX17061@uriah.heep.sax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
> As Nate Williams wrote: > > > NTP, AMD, firewall stuff. Heck, the default 'setup' assumes it can resolve > > hostnames just to configure your IP address, ... > > Huh? No, Nate, we've abandoned this long ago. We are using IP > numbers there to solve the chicken-and-egg problems. So is there a reason for not having named started at the end of network_pass1 rather than at the start of pass2 ? There's even a comment in rc saying that without resolv.conf, we need to start named before syslogd (it's actually started afterwards). The "original" problem that started this thread was that the mount -a -t nfs fails when there's no resolv.conf. > -- > cheers, J"org > > joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE > Never trust an operating system you don't have sources for. ;-) -- Brian <brian@awfulhak.org>, <brian@freebsd.org> <http://www.awfulhak.org>; Don't _EVER_ lose your sense of humour....
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199709152021.VAA07129>