From owner-freebsd-stable Tue Jul 6 17:32: 8 1999 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id EF0E7152E0 for ; Tue, 6 Jul 1999 17:32:04 -0700 (PDT) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id RAA24835 for stable@FreeBSD.org; Tue, 6 Jul 1999 17:32:03 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <199907070032.RAA24835@freeway.dcfinc.com> Subject: FreeBSD toolkit breakage To: stable@FreeBSD.org Date: Tue, 6 Jul 1999 17:32:03 -0700 (MST) Reply-To: chad@DCFinc.com X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I tried to install 2.2.8-1990328-STABLE on a new machine from the release snapshot on the Toolkit CD set. Two problems came up. The first is that the makeflp.bat program didn't understand it was now running in a subdirectory, and tried to invoke things in the \tools director that wasn't there any more. No biggie. But biggie: The install floppy, when told this was a CD-ROM install, failed to find the "releases" directory (and the correct release within it). It instead insisted that the CD was for the wrong release (3.1-something), and we died there. Lucky workaround--we stuck the CD into a handy nearby Linux machine, and did an NFS export of /cdrom. We then did an over-the-LAN install via the NFS mount, which allowed us to specify the path to the correct release. Just a heads-up for y'all if you want to try the same thing. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message