From owner-freebsd-stable  Fri Mar  2 10:52:46 2001
Delivered-To: freebsd-stable@freebsd.org
Received: from wasp.eng.ufl.edu (wasp.eng.ufl.edu [128.227.116.1])
	by hub.freebsd.org (Postfix) with ESMTP id DF99837B71A
	for <stable@freebsd.org>; Fri,  2 Mar 2001 10:52:42 -0800 (PST)
	(envelope-from bob@eng.ufl.edu)
Received: from eng.ufl.edu (scanner.engnet.ufl.edu [128.227.152.221])
	by wasp.eng.ufl.edu (8.9.3/8.9.3) with ESMTP id NAA03997;
	Fri, 2 Mar 2001 13:52:33 -0500 (EST)
Message-ID: <3A9FEBF1.8C1A5AC4@eng.ufl.edu>
Date: Fri, 02 Mar 2001 13:52:33 -0500
From: Bob Johnson <bob@eng.ufl.edu>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386)
X-Accept-Language: en, eo
MIME-Version: 1.0
To: dcs@newsguy.com
Cc: nickhead@folino.com, stable@freebsd.org
Subject: Re: KERNCONF instead of KERNEL?
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> 
> Date: Fri, 02 Mar 2001 23:34:19 +0900
> From: "Daniel C. Sobral" <dcs@newsguy.com>
> Subject: Re: KERNCONF instead of KERNEL?
> 
> nickhead@folino.com wrote:
> > 
> > What is the prefered way to update a remote machine now?  For years, I've run
> a
> > make buildworld, installworld, cd /sys/i386/conf config, build and install a
> > kernel, then reboot.  All through telnet or ssh.  I've never had problems in
> > the past, and all goes well.  Is there a better way to do this on a machine
> > that you can't get to the console?
> 
> Here is the order suggested and the why:
> 
> 1) make buildworld -- because the new kernel may depend on new tools
> (config(8) is a common example, but no the only one).
> 2) make buildkernel -- some programs may depend on new syscalls, so
> build the kernel before installing the world.
> 3) make installkernel -- install a new kernel (the copy of the old one
> is preserved)
> 4) reboot single user -- make sure the new kernel works

You can't reboot to single user mode when you are doing a remote 
update.  He is specifically asking about the best way to do 
a remote update.  You have to do everything multiuser and accept 
the risk, but there is still the question of what order minimizes 
the risk.

 
> 5) mount filesystems, make installworld -- install the rest of the world
> 6) mergemaster -- update /etc -- the new userland tools may require new
> /etc scripts and configuration files.
> 
> - -- 
> Daniel C. Sobral                        (8-DCS)
> dcs@newsguy.com
> dcs@freebsd.org
> capo@the.obscure.bsdconspiracy.net
> 
>         I think you are delusional, but that is OK. Its part of your natural
> charm!

- Bob

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message