From owner-freebsd-hackers Mon Sep 15 17:20:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA06383 for hackers-outgoing; Mon, 15 Sep 1997 17:20:15 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA06374 for ; Mon, 15 Sep 1997 17:20:11 -0700 (PDT) Received: (from grog@localhost) by freebie.lemis.com (8.8.7/8.8.5) id JAA17292; Tue, 16 Sep 1997 09:49:59 +0930 (CST) Message-ID: <19970916094959.44474@lemis.com> Date: Tue, 16 Sep 1997 09:49:59 +0930 From: Greg Lehey To: Brian Somers Cc: Joerg Wunsch , freebsd-hackers@FreeBSD.ORG Subject: Re: Why not DNS (was: nfs startup - perhaps it is a problem) References: <19970915084437.XX17061@uriah.heep.sax.de> <199709152021.VAA07129@awfulhak.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <199709152021.VAA07129@awfulhak.demon.co.uk>; from Brian Somers on Mon, Sep 15, 1997 at 09:21:21PM +0100 Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8250 Fax: +61-8-8388-8250 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Fight-Spam-Now: http://www.cauce.org Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, Sep 15, 1997 at 09:21:21PM +0100, Brian Somers wrote: >> 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). Possibly. I haven't got round to look at the problem, but I have noticed a hang trying to mount nfs file systems at bootup time. I solved it by adding an & at the end of the mount command. The situation is somewhat complicated by the fact that one of the machines has been down for some time, so the mounts can't complete. > The "original" problem that started this thread was that the mount -a > -t nfs fails when there's no resolv.conf. Correct. I wanted to look at that. Greg