From owner-freebsd-current@FreeBSD.ORG  Mon Dec 29 09:53:05 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 ACF2B16A4CE
	for <freebsd-current@freebsd.org>;
	Mon, 29 Dec 2003 09:53:05 -0800 (PST)
Received: from gate.bitblocks.com (bitblocks.com [209.204.185.216])
	by mx1.FreeBSD.org (Postfix) with ESMTP id C299C43D53
	for <freebsd-current@freebsd.org>;
	Mon, 29 Dec 2003 09:53:03 -0800 (PST)
	(envelope-from bakul@bitblocks.com)
Received: from bitblocks.com (localhost [127.0.0.1])
	by gate.bitblocks.com (8.12.10/8.12.10) with ESMTP id hBTHr3xC046306;
	Mon, 29 Dec 2003 09:53:03 -0800 (PST)
	(envelope-from bakul@bitblocks.com)
Message-Id: <200312291753.hBTHr3xC046306@gate.bitblocks.com>
To: Randy Bush <randy@psg.com>
In-reply-to: Your message of "Mon, 29 Dec 2003 08:43:03 PST."
             <E1Ab0Tv-000Cur-Oc@ran.psg.com> 
Date: Mon, 29 Dec 2003 09:53:03 -0800
From: Bakul Shah <bakul@BitBlocks.com>
cc: FreeBSD Current <freebsd-current@freebsd.org>
Subject: Re: 4.9-stable to 5.x 
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Dec 2003 17:53:05 -0000

>   o can i just do the normal upgrade as described in UPDATING
>     (cvsup, buildworld, kernel, installworld, ...) from 4.9 to
>     5.2RC in one leap?

Recently I updated a new Dell desktop from 4.9 to 5.x by
following /usr/src/UPDATING exactly.  In particular I did:

    mv /usr/src usr/src-4.9
    mv /usr/obj/usr/src /usr/obj/usr/src-4.9
    cvsup
    make buildworld buildkernel installkernel
    cp -p /sys/i386/conf/GENERIC.hints /boot/device.hints
    cd /sys/boot; make install
    reboot
    <hit a key to interrupt the countdown after the kernel is loaded>
    boot -s
    mount -u /
    mount -a
    adjkerntz -i
    mergemaster -p
    rm -rf /usr/include/g++
    make installworld
    mergemaster
    reboot

You can boot your old kernel if the first reboot fails.  You
are pretty much commited to running -current after the
installworld so there is not much point in saving /usr/src as
I did.  But make sure you are aware of -current changes and
where to find things in case something goes wrong.  Having
another freebsd machine nearby would be handy.

ACPI gave me trouble so I just disabled it.  This is one
thing worth knowing.  From the boot loader, and before you do
boot -s, you can do
    set hint.acpi.0.disabled=1
If that solves your problem, don't forget to add
    hint.acpi.0.disabled="1"
in /boot/device.hints.  There are finer grained knobs you
can play with.

>   o is 5.2RC a good compromise choice?

Probably.  If you happen to cvsup -current in the middle of
some major commit or breakage you can be in serious trouble.
At least for upgrade purposes -current seem to be reasonably
stable these days.  Even so, after cvsupping I watched the
-current and cvs lists for a while for signs of problems
before attempting the above.  Just unpack 5.2rc sources in
/usr/src and follow the same sequence.