From owner-freebsd-stable@FreeBSD.ORG Mon Aug 21 23:17:04 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ABBD816A4E0 for ; Mon, 21 Aug 2006 23:17:04 +0000 (UTC) (envelope-from byshenknet@byshenk.net) Received: from core.byshenk.net (core.byshenk.net [62.58.73.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id DE3A643D60 for ; Mon, 21 Aug 2006 23:17:03 +0000 (GMT) (envelope-from byshenknet@byshenk.net) Received: from core.byshenk.net (localhost.aoes.com [127.0.0.1]) by core.byshenk.net (8.13.6/8.13.6) with ESMTP id k7LNH0K8068521; Tue, 22 Aug 2006 01:17:00 +0200 (CEST) (envelope-from byshenknet@core.byshenk.net) Received: (from byshenknet@localhost) by core.byshenk.net (8.13.6/8.13.6/Submit) id k7LNH0i4068520; Tue, 22 Aug 2006 01:17:00 +0200 (CEST) (envelope-from byshenknet) Date: Tue, 22 Aug 2006 01:17:00 +0200 From: Greg Byshenk To: freebsd-stable@freebsd.org Message-ID: <20060821231700.GJ633@core.byshenk.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.2i X-Spam-Status: No, score=0.0 required=5.0 tests=UNPARSEABLE_RELAY autolearn=failed version=3.1.4 X-Spam-Checker-Version: SpamAssassin 3.1.4 (2006-07-25) on core.byshenk.net Cc: Ian Smith Subject: Re: 5.5 to 6.1 upgrade X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Aug 2006 23:17:04 -0000 On Mon, Aug 21, 2006 at 11:52:02PM +0200, Stefan Bethke wrote: > Am 21.08.2006 um 18:19 schrieb Ian Smith: > >I recently (without drama) upgraded a 5.4-RELEASE system to > >FreeBSD 5.5-STABLE #1: Tue Aug 1 11:11:20 EST 2006 > >for 'target practice' at least, on the way to 6.1-STABLE > >I was preparing to portupgrade everything next, when I wondered: > >a) should I upgrade from RELENG_5 straight to RELENG_6 or should I be > >stopping off at 6.1-RELEASE along the way first? and > I'd go straight to 6-stable. Make sure you have a good backup, even > if you stop over at 6.1. I see no reason not to go directly to 6-stable (if that is what you plan to run); I've done it with multiple machines, and just jump right to the 6-stable version that is active on the machines running 6.x. Though I've had no problems, I second the recommendation to have a good backup. Also, if you don't have a known-good 6-stable build, you might want to upgrade to the GENERIC kernel. > >b) do I need to upgrade all existing ports (way out of date) before > >the source upgrade, or can I be confident of doing that from 6.1 > >(-R or -S)? > >FWIW: a wee Celeron 300, so minimising upgrade build times is > >desirable. > Unless you have business critical apps running (downtime must be > minimal), you can wait until you've completed the upgrade to 6- > stable, and then run portupgrade -af. If you'd like to run the > portupgrade overnight, you might want to define BATCH, and possibly > set any port building options in /usr/local/etc/pkgtools.conf, > otherwise, the port builds will be frequently interrupted by make > config questions. It shouldn't be necessary to rebuild ports before the upgrade. If there is something running that is critical, you might want to upgrade it first, just be sure, but it probably isn't necessary. I upgraded a workstation with 200+ ports installed, and saw no problems (I can't for certain that nothing was broken before I upgraded the ports, but I experienced no problems). -- greg byshenk - gbyshenk@byshenk.net - Leiden, NL