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

On 2/23/07, Andre Guibert de Bruet <andy_at_siliconlandmark.com> wrote:
> 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)?
>
Just read the man page, and I can't use it due to how I boot my system.

Since, nextboot only allows the specified kernel to be used
temporarily, When the system is booted for the 3rd time it would be
back to the original kernel.  I usually want to use the same kernel on
the next boot.

If I want to use a different kernel I specify it in loader.conf.

I set it up this way so that I could run 4 Linux Test Project (LTP)
tests.  These runs consists of:

   2 runs on /boot/kernel_debug (linux version set to 2.4.2, and 2.6.16)
   2 runs on /boot/kernel_p4_debug (linux version set to 2.4.2, and 2.6.16)

These runs are used to test the status of the linuxolator on FreeBSD/amd64.

Scot
-- 
DISCLAIMER:
No electrons were mamed while sending this message. Only slightly bruised.