In message: <[EMAIL PROTECTED]>
Peter Wemm <[EMAIL PROTECTED]> writes:
: If it does need them, somebody had better tell my systems. I've got old
: 3.x bootblocks on some of them.
Sorry, you are right.
: /boot/loader though is a different story. 'make installkernel' does not
: install the new loader. However, most non-ancient 4.x loaders can
: boot a 5.x kernel sufficiently well that this shouldn't be a crisis. Or,
: they used to be able to when I last tried it (not too long ago).
The big issue is (or at least used to be) device.hints. However, I
see in the Japanese mailing lists they recommend using the 4.x
/boot/loader, interrupting the boot process, typing 'unload' and then
'load /boot/kernel/kernel' followed by 'boot'. It generally will
work, but some machines with ACPI might have issues relating to
interrupt routing (a number of newer machines are known to work with
ACPI interrupt routing, but not PCI BIOS). It seemed safer to
recommend installing a new /boot/loader.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
