Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 02 Mar 2011 17:01:51 -0500
From:      Lowell Gilbert <freebsd-questions-local@be-well.ilk.org>
To:        freebsd-questions@freebsd.org
Subject:   Re: Finish upgrading remote server without physically being there?
Message-ID:  <44lj0x9o6o.fsf@be-well.ilk.org>
In-Reply-To: <4D6E8AB1.3050706@my.gd> (Damien Fleuriot's message of "Wed, 02 Mar 2011 19:21:37 +0100")
References:  <AANLkTin39JjTsts2WwgDUV2QfZL745D0P3DqTkko8TFq@mail.gmail.com> <4D6E6B16.7010508@my.gd> <AANLkTin7sHXsLwBBUmHinDaB3FLOH25_CDy4v82gKFjw@mail.gmail.com> <4D6E6E51.8030708@my.gd> <4439n5bdlj.fsf@be-well.ilk.org> <4D6E8AB1.3050706@my.gd>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
Damien Fleuriot <ml@my.gd> writes:

> On 3/2/11 7:07 PM, Lowell Gilbert wrote:

>> I do this all the time too, but if the new kernel doesn't boot, you
>> end up in more trouble than needing an extra reboot.  The reboot part is
>> definitely important -- you can reboot into multiuser mode and do the
>> installworld that way, but if you have the new utilities and have to
>> drop back to an old kernel, you may have to reinstall the base system.
>> 
>
> No you don't.
>
>
> after you make installkernel
>
> cd /boot
> mv kernel test
> mv kernel.old kernel
> nextboot -k test
> reboot
>
> ...
>
> all goes well
>
> ...
>
> cd /boot
> mv kernel kernel.old
> mv test kernel
> reboot
>
>
> Bless nextboot :)

My point was not to do installworld until after the new kernel had been
shown to boot.  Unless the "make installworld" was supposed to happen
before the first "reboot" in that procedure, I think we're in full
agreement.  



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?44lj0x9o6o.fsf>