Date: Sat, 02 Nov 2002 18:20:04 -0600 (CST) From: Conrad Sabatier <conrads@cox.net> To: Ned Wolpert <wolpert@codeheadsystems.com> Cc: freebsd-current@FreeBSD.ORG Subject: Re: Upgrading 4.7-stable to -current question Message-ID: <XFMail.20021102182004.conrads@cox.net> In-Reply-To: <1036275918.297.8.camel@wolpert.codeheadsystems.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 02-Nov-2002 Ned Wolpert wrote:
> Folks-
>
> I've ran into problem upgrading to -current from RELENG_4 after the
> 'make installkernel' process. One the kernel was installed, I rebooted.
> However, the old 4.7 kernel was loaded instead of the new -current
> kernel. I read from the archive about how the old /modules directory
> can cause problems, when loading the 5.x kernel, but that's not the
> issue since the wrong kernel was loaded in the first place. Now, when I
> forced /boot/kernel/kernel, the system failed completely. (No error
> message, the loading never occurred as the whole system froze.) Could
> that have been from the old /modules directory?
>
> Anyways, the question is when doing an upgrade, what's the best method
> to update the loader? It isn't installed by default. (From what I could
> tell)
Read the UPDATING file very carefully. You'll see that one of the steps in
upgrading from 4.x to 5.0 is updating the boot blocks.
--
Conrad Sabatier <conrads@cox.net>
"Given the choice between accomplishing something and just lying
around, I'd rather lie around. No contest."
-- Eric Clapton
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.20021102182004.conrads>