From owner-freebsd-questions@FreeBSD.ORG Thu Oct 20 00:54:26 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CC1271065673 for ; Thu, 20 Oct 2011 00:54:26 +0000 (UTC) (envelope-from ml@my.gd) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 607158FC14 for ; Thu, 20 Oct 2011 00:54:23 +0000 (UTC) Received: by wwi18 with SMTP id 18so3339779wwi.31 for ; Wed, 19 Oct 2011 17:54:23 -0700 (PDT) Received: by 10.227.38.89 with SMTP id a25mr3309937wbe.70.1319072063060; Wed, 19 Oct 2011 17:54:23 -0700 (PDT) Received: from [192.168.0.47] (paris.c-mal.com. [88.170.200.60]) by mx.google.com with ESMTPS id es5sm12830675wbb.11.2011.10.19.17.54.20 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 19 Oct 2011 17:54:21 -0700 (PDT) References: In-Reply-To: Mime-Version: 1.0 (iPhone Mail 8J2) Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Message-Id: X-Mailer: iPhone Mail (8J2) From: Damien Fleuriot Date: Thu, 20 Oct 2011 02:54:13 +0200 To: Kurt Buff Cc: "freebsd-questions@freebsd.org" Subject: Re: Upgrading from 6.2-RELEASE? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Oct 2011 00:54:26 -0000 On 19 Oct 2011, at 21:45, Kurt Buff wrote: > On Wed, Oct 19, 2011 at 12:03, Chuck Swiger wrote: >> On Oct 19, 2011, at 11:55 AM, Kurt Buff wrote: >>> I have gotten custody of an old machine running the aforementioned, >>> and it's in production. I can take it down for a couple of hours if >>> necessary, but would prefer to have it down as little as possible. >>=20 >> The most straightforward solution would be to build out and validate a ne= w system running FreeBSD-7.4 or 8.2, and drop it in place of the old box. I= f all is good, decommission the old hardware. >=20 > I agree. I've already got a new VM started with 8.2. I'm trying to see > if I can migrate the data to the new host, but it's not finished yet, > and the old box's ports aren't functioning and can't be upgraded, so > I'm stuck in a bit of a scramble. >=20 >>> What are my options for getting it to a supported release - looking at >>> the handbook it doesn't appear the the freebsd-update utility will >>> work in this case, as it's not 6.3? Can I, for instance, boot from a >>> CD of a supported version and do an upgrade, or am I stuck doing a >>> download of sorce for 7.0-RELEASE, compiling that, and then an >>> freebsd-update to 7.4? >>=20 >> You can do either. However, it's probably easier to just download and bu= rn the 7.4 or 8.2 image, and do an upgrade directly than it would be do upgr= ade via source to 7.0-RELEASE and then try freebsd-update. >=20 > Gotta love conflicting answers from you and Adam >=20 I'll give you more conflict. I'd do source upgrades from 6.2 -> 6.3 -> 7.0 -> 7.4 -> 8.0 -> 8.2 Or at the very least 6.2 -> 7.0 -> (8.0 ->) 8.2 The idea here is to get to the latest stable version of a branch, then hop t= o the lowest version of the next one, rince/repeat. This way, imo, you update more progressively and bit by bit. I wouldn't be confident doing for instance 6.2 -> 8.2 And I'd be even muuuuuch less confident running binary upgrades or upgrades f= rom CD. I think a CD upgrade will not update your config files properly for instance= . You'll be missing new system accounts (like hast for example), you'll have e= xtra init scripts lying around, you'll miss some, you'll miss stuff from per= iodic, startup script fixes... Do not do a binary upgrade for major version hops. Read UPDATING carefully and consider its contents take precedence over the w= ebsite/handbook.=