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

On Feb 23, 2007, at 3:50 AM, Scot Hetzel wrote:

> On 2/23/07, Andre Guibert de Bruet <andy_at_siliconlandmark.com> wrote:
>> 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.

Gotcha. One thing that it lets you easily do is boot in single-user  
mode upon reboot (Using -o "-s") without having to babysit the  
machine. I use it to test throw-away kernels with untested changes,  
in a VM.

Andy

/*  Andre Guibert de Bruet  * 6f43 6564 7020 656f 2e74 4220 7469 6a20 */
/*   Code poet / Sysadmin   * 636f 656b 2e79 5320 7379 6461 696d 2e6e */
/*   GSM: +1 734 846 8758   * 5520 494e 2058 6c73 7565 6874 002e 0000 */
/* WWW: siliconlandmark.com * C/C++, Java, Perl, PHP, SQL, XHTML, XML */