>
> Date: Fri, 02 Mar 2001 23:34:19 +0900
> From: "Daniel C. Sobral" <[EMAIL PROTECTED]>
> Subject: Re: KERNCONF instead of KERNEL?
>
> [EMAIL PROTECTED] 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)
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]
>
> I think you are delusional, but that is OK. Its part of your natural
> charm!
- Bob
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
