From owner-freebsd-stable@FreeBSD.ORG  Thu Oct 16 06:29:37 2003
Return-Path: <owner-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 2954A16A4BF
	for <stable@freebsd.org>; Thu, 16 Oct 2003 06:29:37 -0700 (PDT)
Received: from be-well.ilk.org (lowellg.ne.client2.attbi.com [66.30.200.37])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 360C843FB1
	for <stable@freebsd.org>; Thu, 16 Oct 2003 06:29:36 -0700 (PDT)
	(envelope-from freebsd-stable-local@be-well.ilk.org)
Received: by be-well.ilk.org (Postfix, from userid 1147)
	id 9E47A3B04; Thu, 16 Oct 2003 09:29:35 -0400 (EDT)
Sender: lowell@be-well.ilk.org
To: stable@freebsd.org
References: <55492.207.5.142.198.1066307656.squirrel@bmyster.com>
From: Lowell Gilbert <freebsd-stable-local@be-well.ilk.org>
Date: 16 Oct 2003 09:29:35 -0400
In-Reply-To: <55492.207.5.142.198.1066307656.squirrel@bmyster.com>
Message-ID: <44n0c1z4xs.fsf@be-well.ilk.org>
Lines: 100
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: updating system help ??!!??
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: stable@freebsd.org
List-Id: Production branch of FreeBSD source code
	<freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Oct 2003 13:29:37 -0000

"Brent Bailey" <misterb@bmyster.com> writes:

> Im running several Freebsd systems  some are rather old FBSD 4.6 but most
> are at the 4.8rc1 level. anyway does the below procedure for updating a
> Freebsd system seem like the correct way for both older and newer systems
> ??
> any and all help is very appreciated
> Thank you
>=20
>=20
> ###########################
> Backup /etc:
>=20
> # cp -Rp /etc /etc.old
>=20
>=20
> Run mergemaster in pre-buildworld mode to update files essential to the
> success of buildworld and installworld:
>=20
> # /usr/sbin/mergemaster -p
>=20
>=20
> Remove old /usr/obj:
>=20
> # cd /usr/obj
> # chflags -R noschg *
> # rm -rf *
>=20
>=20
> Compile the sources:
>=20
> # cd /usr/src
> # make buildworld
>=20
>=20
> Compile and install the new kernel:
>=20
> # cd /usr/src (if you've changed directories after the last step)
> # make kernel KERNCONF=3DYOURKERNEL
>=20
> If you don't already have a custom kernel configuration, use GENERIC in
> place of YOURKERNEL above. If you wish to create a custom kernel, see the
> Building a Custom Kernel cheat sheet.
>=20
>=20
> Drop to single user mode:
> # shutdown now
>=20
>=20
> Or reboot into single user mode:
>=20
> # shutdown -r now
> =B7=B7=B7
> Ok boot -s

The latter, not the former.=20=20
You want to be running the *new* kernel before starting the system install.

> # fsck -p
> # mount -u /
> # mount -a -t ufs
> # swapon -a
> # adjkerntz -i
>=20
>=20
> Install the new system binaries:
> # cd /usr/src
> # make installworld
>=20
>=20
> Update system configuration files:
> # /usr/sbin/mergemaster -v -w 132 (eliminate '-w 132' if 132x43 video mode
> is not activated)
>=20
>=20
> Update /dev
>=20
> In most cases, mergemaster will realize when it is necessary to update the
> devices, and will offer to complete it automatically. If you've declined
> mergemaster's offer, perform these steps to update /dev manually:
>=20
> # cd /dev
> # /bin/sh MAKEDEV all
>=20
>=20
> Update /stand:
>=20
> This step is included for completeness. It can be safely omitted.
>=20
> # cd /usr/src/release/sysinstall
> # make clean
> # make all install
>=20
>=20
> Reboot to multi-user mode:
>=20
> # reboot

With the one proviso listed above, it's okay.
I'm not sure why you keep posting this, though...