RE: 4.5-5.0 New Bootloader needed
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of [EMAIL PROTECTED] Sent: Tuesday, March 12, 2002 10:05 PM To: [EMAIL PROTECTED] 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 [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 4.5-5.0 New Bootloader needed
At Wed, 13 Mar 2002 09:14:09 +0100,
Jan Stocker wrote:
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of
[EMAIL PROTECTED]
Sent: Tuesday, March 12, 2002 10:05 PM
To: [EMAIL PROTECTED]
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 [EMAIL PROTECTED]
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]
reboot
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 [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: 4.5-5.0 New Bootloader needed
On Wed, Mar 13, 2002 at 09:14:09AM +0100, Jan Stocker wrote: -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of [EMAIL PROTECTED] Sent: Tuesday, March 12, 2002 10:05 PM To: [EMAIL PROTECTED] 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? It should be taken care of by installworld when it installs new config files for the loader, right? i.e. the /boot/kernel location for the 5.0 kernel is specified in the default config file. Kris msg36022/pgp0.pgp Description: PGP signature
Re: 4.5-5.0 New Bootloader needed
Kris Kennaway wrote: It should be taken care of by installworld when it installs new config files for the loader, right? i.e. the /boot/kernel location for the 5.0 kernel is specified in the default config file. I think the point here is that when upgrading, you should boot the new kernel *before* running the installworld (and thus before installing the new loader). If you're not paying attention (or don't know better) you'll boot the old kernel instead and possibly have a bad time. This is in fact mentioned in UPDATING already, but it's a bit buried in the more mundane items. It's also confusing that it's not mentioned in the section about the 4.x - 5.0 dance. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
