From owner-freebsd-current Wed Mar 13 0:35:15 2002 Delivered-To: freebsd-current@freebsd.org Received: from kylebutt.dorms.usu.edu (kylebutt.dorms.usu.edu [129.123.231.119]) by hub.freebsd.org (Postfix) with ESMTP id E5A4637B400 for ; Wed, 13 Mar 2002 00:35:11 -0800 (PST) Received: from kylebutt.dorms.usu.edu (6dd342c2c8f145575a94c965af3c9fdb@localhost [127.0.0.1]) by kylebutt.dorms.usu.edu (8.12.2/8.12.2) with ESMTP id g2DEIGsx082049; Wed, 13 Mar 2002 07:18:19 -0700 (MST) (envelope-from kylebutt@myrealbox.com) Date: Wed, 13 Mar 2002 07:18:16 -0700 Message-ID: <87henkr1p3.wl@kylebutt.dorms.usu.edu> From: Kyle Butt To: Cc: Subject: Re: 4.5->5.0 New Bootloader needed In-Reply-To: <000001c1ca67$0d5067a0$fe02010a@twoflower.liebende.de> References: <200203122105.g2CL56p02307@hunkular.glarp.com> <000001c1ca67$0d5067a0$fe02010a@twoflower.liebende.de> User-Agent: Wanderlust/2.8.1 (Something) SEMI/1.14.3 (Ushinoya) FLIM/1.14.3 (=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 Emacs/21.1 (i386--freebsd) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII 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 At Wed, 13 Mar 2002 09:14:09 +0100, Jan Stocker wrote: > > > > > -----Original Message----- > > From: owner-freebsd-current@FreeBSD.ORG > > [mailto:owner-freebsd-current@FreeBSD.ORG]On Behalf Of > > huntting@glarp.com > > Sent: Tuesday, March 12, 2002 10:05 PM > > To: current@FreeBSD.ORG > > Subject: 4.5->5.0 kldxref:No such file or directory > > > > As an asside, I've noticed in the past when upgrading from 4.0 to > > 5.0, I've had to forcebly reinstall the loader. I dont know why, > > but the loader shiped with (at least) 4.4 doesnt seem to like > > loading 5.0 kernel bits. > > If i understand the boot procedure right it isnt the the mbr but the boot > sector of the partition. For 5.0 the kernel and modules stuff can be found > unter /boot not in the root-tree. So after a buildkernel and installkernel > none of the boot sectors are overwritten and the old kernel will be loaded. > > I think this has to be mentioned in the UPDATING text should it? > > Jan > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > This changes after the installworld target. From UPDATING: To upgrade from 4.x-stable to current ------------------------------------- make buildworld make buildkernel KERNCONF=YOUR_KERNEL_HERE cp src/sys/${MACHINE_ARCH}/conf/GENERIC.hints /boot/device.hints [2] make installkernel KERNCONF=YOUR_KERNEL_HERE reboot in single user [3] make installworld mergemaster [4] [1] I updated my machine from 4.5-stable to 5.0-current without a hang up, but I did notice that after I installed the kernel it didn't boot it. But after the installworld it did. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message