From owner-freebsd-current Mon Dec 27 11:34:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 71A12152C2 for ; Mon, 27 Dec 1999 11:34:41 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id UAA05412; Mon, 27 Dec 1999 20:34:27 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Forrest Aldrich Cc: freebsd-current@FreeBSD.ORG Subject: Re: Installation bug (4.0-19991227-CURRENT) In-reply-to: Your message of "Mon, 27 Dec 1999 14:14:29 EST." <4.2.2.19991227141115.00a98f00@216.67.12.69> Date: Mon, 27 Dec 1999 20:34:27 +0100 Message-ID: <5410.946323267@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <4.2.2.19991227141115.00a98f00@216.67.12.69>, Forrest Aldrich writes : >Did a test install against the latest snapshot. > >The network configuration comes up with "dc0" (we have de0), this >"works" in that we were able to perform the network install (so it >must be a typo somewhere). No, dc0 is the new and improved driver for the newer tulip chips. >However, it results in multiple entries in /etc/rc.conf (three, >total), which have to be removed before the network will come up >correctly after rebooting. > >NB, this was an install over a previous 4.0 instance, so there's >the possibility that the rc.conf file was edited rather than written >over -- though I would doubt that (?). That is probably what happened here. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message