From owner-freebsd-current Sat Nov 2 16:20:25 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8062837B401 for ; Sat, 2 Nov 2002 16:20:24 -0800 (PST) Received: from ip68-14-62-49.no.no.cox.net (ip68-14-62-49.no.no.cox.net [68.14.62.49]) by mx1.FreeBSD.org (Postfix) with ESMTP id D80A843E3B for ; Sat, 2 Nov 2002 16:20:23 -0800 (PST) (envelope-from conrads@cox.net) Received: from ip68-14-62-49.no.no.cox.net (localhost [127.0.0.1]) by ip68-14-62-49.no.no.cox.net (8.12.6/8.12.6) with ESMTP id gA30K9xS021285; Sat, 2 Nov 2002 18:20:17 -0600 (CST) (envelope-from conrads@ip68-14-62-49.no.no.cox.net) Received: (from conrads@localhost) by ip68-14-62-49.no.no.cox.net (8.12.6/8.12.6/Submit) id gA30K4vG021284; Sat, 2 Nov 2002 18:20:04 -0600 (CST) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.5.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <1036275918.297.8.camel@wolpert.codeheadsystems.com> Date: Sat, 02 Nov 2002 18:20:04 -0600 (CST) Reply-To: conrads@cox.net Organization: A Rag-Tag Band of Drug-crazed Hippies From: Conrad Sabatier To: Ned Wolpert Subject: Re: Upgrading 4.7-stable to -current question Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG 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 "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