From owner-freebsd-stable Sun Dec 19 11:19:58 1999 Delivered-To: freebsd-stable@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id 33E9E14E40; Sun, 19 Dec 1999 11:19:57 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 57C551C2B; Sun, 19 Dec 1999 14:19:30 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by jade.chc-chimes.com (Postfix) with ESMTP id 4A96B381B; Sun, 19 Dec 1999 14:19:30 -0500 (EST) Date: Sun, 19 Dec 1999 14:19:30 -0500 (EST) From: Bill Fumerola To: Mike Smith Cc: Ben Goodwin , Oliver Blasnik , "Jeffrey J. Libman" , freebsd-stable@FreeBSD.ORG Subject: Re: mountd and rpc.statd won't run In-Reply-To: <199912191816.KAA02792@mass.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 19 Dec 1999, Mike Smith wrote: > > Indeed I ran into this problem just yesterday. I have found that all my > > 3.3-RELEASE boxes didn't configure a lo0 by default! I'd consider that a > > bug :-) > > You'd be wrong. There's an ifconfig_lo0 entry in the defaults file. Don't be so sure that he's wrong. We installed a lot of 3.3 machines here when it first came out and some of them had NIS issues which actually were the result of lo0 not being configured by default. It didn't happen on every machine which led me to believe it was probably different sysinstall incantations that did it, unfortunatly I didn't have time to track down exactly what those incantations were. -- - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message