Re: Unable to use network early in boot with recent -current

> From: Andre Guibert de Bruet <andy_at_siliconlandmark.com>
> Date: Fri, 23 Feb 2007 02:21:44 -0500
> 
> On Feb 22, 2007, at 2:29 AM, Scot Hetzel wrote:
> 
> > On 2/21/07, Skip Ford <skip.ford_at_verizon.net> wrote:
> >> Kevin Oberman wrote:
> >> > Any thought of making module loads default to the directory of the
> >> > booted kernel (e.g. /boot/kernel.old) instead of /boot/kernel?
> >>
> >> This should already happen if you "set kernel" to kernel.old and
> >> then "boot".
> >
> > I set the kernel variable in loader.conf, so that I can have multiple
> > kernels installed and choose which kernel to boot the next time the
> > server is booted.
> >
> > /boot/loader.conf
> > #kernel="kernel_p4_debug"
> > kernel="kernel_debug"
> >
> > hp010# sysctl -a | grep kernel
> > kern.bootfile: /boot/kernel_debug/kernel
> > kern.module_path: /boot/kernel_debug;/boot/modules
> 
> Just out of curiosity, have you come across nextboot(8)?

Good idea! nextboot(8) was broken in current for quite a while and I
guess I pretty much forgot about it. 

It really does not make any difference. It boots the requested kernel
and loads all modules requested by loader.conf, but, when I try loading
modules after the boot, I still get the warning that the module is newer
than the linker.hints file.

kern.module_path: /boot/kernel.old;/boot/modules

So nextboot(8) makes no difference, but it is handy and it had completely
escaped my conscience.

Thanks!
-- 
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: oberman_at_es.net			Phone: +1 510 486-8634
Key fingerprint:059B 2DDF 031C 9BA3 14A4  EADA 927D EBB3 987B 3751