From owner-freebsd-current Sun Nov 29 15:24:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA14972 for freebsd-current-outgoing; Sun, 29 Nov 1998 15:24:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from snark.wizard.com (snark.wizard.com [199.171.28.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA14965 for ; Sun, 29 Nov 1998 15:24:25 -0800 (PST) (envelope-from ernst@snark.wizard.com) Received: (from ernst@localhost) by snark.wizard.com (8.9.0/8.9.0) id PAA15835; Sun, 29 Nov 1998 15:24:14 -0800 (PST) Date: Sun, 29 Nov 1998 15:24:13 -0800 (PST) From: "Richard B. Ernst" To: "Jordan K. Hubbard" cc: Stephen McKay , freebsd-current@FreeBSD.ORG Subject: Re: 2.2.7-->current shortcut *boom* In-Reply-To: <20475.912381262@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've thought about that, and most likely will end up doing so. I'd just wanted to be able to do a behind-the-scenes upgrade so user impact would be minimal. Managed to do that from 2.2.5-->2.2.6-->2.2.7. Is the "Upgrade" option from sysinstall on a booted floppy the way to go, or... ? Thanks ----- On Sun, 29 Nov 1998, Jordan K. Hubbard wrote: :>> Still no joy on getting -current (from CVS) to compile on a very mixed up :>> system. More suggestions? :> :>Maybe unmix the system by doing a fresh installation before attempting :>any further to untangle this knot from the inside? :) :> :>- Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message