From owner-freebsd-current Sat Nov 2 16:59: 1 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 30ED537B401 for ; Sat, 2 Nov 2002 16:59:00 -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 45EBC43E97 for ; Sat, 2 Nov 2002 16:58:59 -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 gA30wqxS020184; Sat, 2 Nov 2002 18:58:52 -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 gA30wlWv020183; Sat, 2 Nov 2002 18:58:47 -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: <1036284227.297.26.camel@wolpert.codeheadsystems.com> Date: Sat, 02 Nov 2002 18:58:47 -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 03-Nov-2002 Ned Wolpert wrote: > 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? Mmm, perhaps not. :-) > 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 Yes, that's the one I was thinking of, actually. Had a little slip of the brain there. :-) > 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? I do think this last step (make install in sys/boot) is an absolute "must" to boot the new kernel. Someone may correct me, but that's the impression I got from reading the docs. Myself, I played it ultra-safe and followed the upgrade instructions to the letter, including moving the 4.x modules to a different directory. The upgrade went off without a single gotcha. -- Conrad Sabatier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message