From owner-freebsd-current Sun Feb 15 16:07:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA20748 for freebsd-current-outgoing; Sun, 15 Feb 1998 16:07:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA20742 for ; Sun, 15 Feb 1998 16:07:21 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id QAA03733; Sun, 15 Feb 1998 16:06:50 -0800 (PST) Message-Id: <199802160006.QAA03733@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Superuser cc: current@FreeBSD.ORG Subject: Re: Preferred way (or FAQ) for upgrading 2.2 to 3.0-CURRENT In-reply-to: Your message of "Sun, 15 Feb 1998 22:50:53 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 15 Feb 1998 16:06:49 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi > > Should I use cvsup or current boot.flp for upgrade ? -current snapshots for the last week or so have been broken. It's relatively straightforward to bootstrap up from 2.2, presuming that you are willing to deal with upgrading /etc/, remember to install the new X binaries, and deal with the changed utmp/wtmp format. > I have 2*200PPro system running 2.2-STABLE and would like to use second > CPU as well... have successfully tested 3.0-CURRENT on monoprocessor 486 > system. If this is a production system, I would hold off at the moment. If you're using it as a workstation or a personal box, then by all means give it a go. You might also want to consider reinstalling from a SNAP from very early February (say 5th or before), then cvsup at will. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message