tech-kern archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

default boot.cfg, netbsd.old, onetbsd [was: Re: drivers (not?) utilising pcidevs data]



Patrick Welche wrote:
On Fri, Feb 16, 2018 at 10:36:33AM +0100, Martin Husemann wrote:
Depends on when you attach the device and how you load modules.
You can make the bootloader pre-load them via /boot.cfg - or build them
into the kernel.

Hijacking mention of /boot.cfg: I accidentally booted a test box
which had /netbsd.old but no /netbsd. My recollection is that if
/netbsd was bad, /netbsd.old would be tried instead. That didn't
appear to happen, and I needed a trip into the server room and a
hunt for a monitor etc. (My recollection may predate the existence
of /boot.cfg - did something change? The box does have a /boot.cfg
as per default.)

The default boot.cfg specifies the kernel name explicitly as
"netbsd" (https://nxr.netbsd.org/xref/src/etc/etc.amd64/boot.cfg#1) so the boot process does not use the alternative names (https://nxr.netbsd.org/xref/src/sys/arch/i386/stand/boot/boot2.c#459, https://nxr.netbsd.org/xref/src/sys/arch/i386/stand/boot/boot2.c#98).

IMO the default boot.cfg entry should omit the explicit kernel name to enable fallback by default.

r.


Home | Main Index | Thread Index | Old Index