From owner-freebsd-questions Fri Apr 7 22:48:14 2000 Delivered-To: freebsd-questions@freebsd.org Received: from rjk191.rh.psu.edu (RJK191.rh.psu.edu [128.118.193.182]) by hub.freebsd.org (Postfix) with ESMTP id 85EB137BABD for ; Fri, 7 Apr 2000 22:48:11 -0700 (PDT) (envelope-from ray@rjk191.rh.psu.edu) Received: (from ray@localhost) by rjk191.rh.psu.edu (8.9.3/8.9.3) id BAA14097 for freebsd-questions@FreeBSD.ORG; Sat, 8 Apr 2000 01:48:10 -0400 (EDT) (envelope-from ray) Date: Sat, 8 Apr 2000 01:48:10 -0400 From: Ray Kohler To: freebsd-questions@FreeBSD.ORG Subject: Re: Upgrading 3.2-RELEASE to 4.0-RELEASE Message-ID: <20000408014810.B14065@rjk191.rh.psu.edu> Reply-To: rjk191@psu.edu References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from netcmd@networkcommand.com on Sat, Apr 08, 2000 at 02:23:29AM +0000 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Apr 08, 2000 at 02:23:29AM +0000, Jon O. wrote: > I think I'm going to restore and upgrade with cvsup. Assistance with that > would be helpful too. But, I think if sysinstall is an option the user > should be told how to do it that way and not just the quote above. I can't really tell you anything about upgrading with sysinstall other than it is good for upgrading when the major version is the same, and bad otherwise. As for cvsup, this is the normal way to do it. If you're familiar with 'make world' and friends, this will make it easier. _BUT_ regardless of what you do or don't know, you need to read the file /usr/src/UPDATING after retrieving the new version along with the rest of the cvsup. Following these instructions is the only safe and successful way to go from 3.X to 4.0 without getting hit by the 'gotchas'. -- Ray Kohler FreeBSD -- The Power to Serve Information Center, n.: A room staffed by professional computer people whose job it is to tell you why you cannot have the information you require. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message