From owner-freebsd-current@FreeBSD.ORG Tue Jan 6 10:15:40 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E012916A4CE for ; Tue, 6 Jan 2004 10:15:40 -0800 (PST) Received: from sccrmhc11.comcast.net (sccrmhc11.comcast.net [204.127.202.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id A964543D2D for ; Tue, 6 Jan 2004 10:15:39 -0800 (PST) (envelope-from DougB@freebsd.org) Received: from master.dougb.net (c-24-130-160-161.we.client2.attbi.com[24.130.160.161]) by comcast.net (sccrmhc11) with SMTP id <2004010618153801100sfi73e>; Tue, 6 Jan 2004 18:15:38 +0000 Date: Tue, 6 Jan 2004 10:15:37 -0800 (PST) From: Doug Barton To: Benjamin Close In-Reply-To: <3FF9EE96.50207@cs.unisa.edu.au> Message-ID: <20040106101307.D88773@znfgre.qbhto.arg> References: <3FF9EE96.50207@cs.unisa.edu.au> Organization: http://www.FreeBSD.org/ X-message-flag: Outlook -- Not just for spreading viruses anymore! MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: "freebsd-current@freebsd.org" Subject: Re: Upgrading from 4.5->5.2 breaks in rescue/rescue/common X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Jan 2004 18:15:41 -0000 On Tue, 6 Jan 2004, Benjamin Close wrote: > Garance A Drosihn wrote: > > > If it were me, I would first try to upgrade to 4.9-"safe" > > aka 4.9-"security", make sure that was OK, and then jump > > to 5.x. Obviously that's more work, so I wouldn't blame > > you too much if you wanted to avoid the extra builds. > > > > Also, I am not sure that would solve the problem you care > > about right now... I'm just saying that's the way I tend > > to do things. > > Yeah, I wanted to avoid doing this. It's never been supported to upgrade to -current from anything less than the most recent -stable. The fact that it accidentally works sometimes is purely coincidence. Also, it's highly recommended that you actually back up your important files and do a clean install of a new branch. This is especially useful for 5.x because you can take advantage of the opportunity to newfs your file systems with UFS2. You can of course pursue the beating your head against the wall path, it's your time. Just don't be surprised when it doesn't work. Good luck, Doug -- This .signature sanitized for your protection