From owner-freebsd-questions@FreeBSD.ORG Thu May 17 10:39:40 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4673C16A405 for ; Thu, 17 May 2007 10:39:40 +0000 (UTC) (envelope-from d.hill@yournetplus.com) Received: from duane.dbq.yournetplus.com (duane.dbq.yournetplus.com [65.124.230.214]) by mx1.freebsd.org (Postfix) with ESMTP id 25C0313C44B for ; Thu, 17 May 2007 10:39:40 +0000 (UTC) (envelope-from d.hill@yournetplus.com) Received: from [192.168.1.10] (unknown [192.168.1.1]) by duane.dbq.yournetplus.com (Postfix) with ESMTP id 7478E2E0037 for ; Thu, 17 May 2007 10:39:35 +0000 (UTC) Date: Thu, 17 May 2007 10:39:35 +0000 (UTC) From: Duane Hill X-X-Sender: d.hill@duane.dbq.yournetplus.com To: freebsd-questions@freebsd.org In-Reply-To: <464BCE1A.4020400@infracaninophile.co.uk> Message-ID: <20070517102831.O61920@duane.dbq.yournetplus.com> References: <20070516182846.C34584@duane.dbq.yournetplus.com> <464BCE1A.4020400@infracaninophile.co.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Re: amd64 FreeBSD Release 5.5 -> 6.2 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, 17 May 2007 10:39:40 -0000 On Thu, 17 May 2007, Matthew Seaman wrote: > Duane Hill wrote: >> >> I have a server that, at first, required 5.5 because of the MTA that was >> running on the server. It no longer is running that particular MTA >> anymore. I need to upgrade the server to release 6.2. >> >> Is it just a matter of changing the release tag within the cvsup file >> from RELENG_5_5 to RELENG_6_2, removing the contents of /usr/src/*, >> removing the contents of /usr/obj/*, and doing a clean cvsup? > > Pretty much. You don't actually need to delete /usr/src/*, and not > doing so will save you some bandwidth. > > You should be able to upgrade the system by a routine buildworld, > buildkernel ... type operation, but beware that you will need to > recompile all of your ports because of potential shlib version > clashes. Ports from 5.5 will still work on 6.2, but later trying to > update them piecemeal can lead to misery. I'm using portupgrade. So I will use the switches force a reinstall and to act on everything that depends on the reinstalled port (-fr).