From owner-freebsd-questions@FreeBSD.ORG Fri Jul 15 21:12:53 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 250EC106566B for ; Fri, 15 Jul 2011 21:12:53 +0000 (UTC) (envelope-from repcsike@gmail.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id A3E508FC0C for ; Fri, 15 Jul 2011 21:12:52 +0000 (UTC) Received: by wyg24 with SMTP id 24so1423573wyg.13 for ; Fri, 15 Jul 2011 14:12:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=Vk9ztWt3xj1y9BKFHAk5wum5N86Cvdbdq9thmN5IXF4=; b=USy8K1ae5MZbhehzrYYiL17apR5nDOsHHkobvoxTjONgZV7zZE55ZKCDMEFfN3/J4M 0TsWsHJRwoHbREijtEqvr0GK/USt6Mg8Yd3V2oSgKs4zLa7GRcA11qF3rRYHznsTc/2V VE1yHzvhyjBWE79tN8LEDZz0GqPSNd9eLEwC4= MIME-Version: 1.0 Received: by 10.227.174.201 with SMTP id u9mr3386714wbz.53.1310764371443; Fri, 15 Jul 2011 14:12:51 -0700 (PDT) Received: by 10.227.146.138 with HTTP; Fri, 15 Jul 2011 14:12:51 -0700 (PDT) In-Reply-To: <20110715204615.GB12391@slackbox.erewhon.net> References: <20110715204615.GB12391@slackbox.erewhon.net> Date: Fri, 15 Jul 2011 23:12:51 +0200 Message-ID: From: =?ISO-8859-1?B?QmFs4XpzIE3hdOlmZnk=?= To: FreeBSD Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: Upgrading very old installation 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: Fri, 15 Jul 2011 21:12:53 -0000 On 15 July 2011 22:46, Roland Smith wrote: > On Fri, Jul 15, 2011 at 08:20:52AM -0400, Jaime Kikpole wrote: > > I'm running a FreeBSD 6.x server that hasn't been updated in about 1.5 > years. > > > > atlas:~>uname -mprs > > FreeBSD 6.4-RELEASE-p8 i386 i386 > > > I've been using the cvsup/make method of upgrades for years and only > > used freebsd-upgrade once. I'm not sure if either method can handle a > > 6.x to 8.x upgrade. > > They are tested for upgrading to the next major version. Who knows if it > will > work across two major versions? Personally I wouldn't want to be the one ot > try it out. :-) > > > I also have a bunch of ports in this server (e.g. apache, postfix, > > etc.) Once the OS is updated, should I just portupgrade them all? > > Doesn't work reliably across major version updates. When updating to a > newer > major version, the best way is to delete all ports (save their config files > of course), scrub the /usr/local tree clean and then re-install them. > > Matthews advice of re-installing 8.2 on a second harddrive is probably the > easiest and safest way to go. > > Roland > -- > R.F.Smith http://www.xs4all.nl/~rsmith/ > [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] > pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) > Hi, I would try to update the split mirror of the 6.4 to 8.2, I did manage to update couple of years back from Releng6 to Current 8 :). Did the usual make kernel / world stuff mergemaster prebuild in the middle and mergemaster after the update then I rebuilt all the ports. I recently did a 6.4-STABLE > 8.2-RELEASE-p2 migration to another server, but without using only some initial old config files from the old system because I had to build a better environment with other software for the same role (almost the same thing that Matt recommended you). For me this is a longer procedure then updating all the software and checking for maybe now deprecated options and other problems. So I think its down to your level of knowledge and personal preference ( whether you want to check what is to problem in case something goes wrong- I like this because I get to know the system and the inner workings in more detail). I personally don't like freebsd-update, and if your are new to the build from source way, you should really go with building up from scratch, then migrate. In case you want to update have a WORKING backup, and do a test run for the update (restore your 6.4 on a test machine and try to update it) before you bring down the productive system. Good luck! Regards, Balazs.