From owner-freebsd-current Sat Nov 2 16:41:12 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 6728B37B401 for ; Sat, 2 Nov 2002 16:41:11 -0800 (PST) Received: from www.codeheadsystems.com (codeheadsystems.com [68.14.217.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id D2AF043E91 for ; Sat, 2 Nov 2002 16:41:10 -0800 (PST) (envelope-from wolpert@codeheadsystems.com) Received: from [192.168.1.50] (wolpert.codeheadsystems.com [192.168.1.50]) by www.codeheadsystems.com (8.12.6/8.12.3) with ESMTP id gA30f3Zp018210; Sat, 2 Nov 2002 17:41:03 -0700 (MST) (envelope-from wolpert@codeheadsystems.com) Subject: Re: Upgrading 4.7-stable to -current question From: Ned Wolpert To: conrads@cox.net Cc: freebsd-current@FreeBSD.ORG In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 Date: 02 Nov 2002 17:43:47 -0700 Message-Id: <1036284227.297.26.camel@wolpert.codeheadsystems.com> Mime-Version: 1.0 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 Sat, 2002-11-02 at 17:20, Conrad Sabatier wrote: > 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. Yes, there are several entries. 20000615 is the most interesting: In addition, you'll need to update your boot blocks to a more modern version, if you haven't already done so. Modern here means 4.0 release or newer (although older releases may work). Now, my system was installed around 4.4, so I "should not" need to update my boot blocks. Correct? Getting back to my original question, the problem I was having was with the loader itself. Now, do I have to execute this step (from the UPDATING document) cd src/sys/boot ; make install Reason why I ask is because my loader is from 4.4, so it should work. (Provided I do a ok unload ok boot /boot/kernel/kernel manually) As the UPDATING doc mentions, upgrading from 4.x to 5.x needs that step to avoid those extra steps, yes? But it should still boot if I unload and load manually, correct? I guess the real question was that if this is the case, it didn't boot into /boot/kernel/kernel at that point either... after the unload and boot steps above. Could that have occurred because I still had the old /modules directory? -- Virtually, Ned Wolpert 4e75 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message