Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 09 Apr 2001 00:00:32 -0300
From:      "Daniel C. Sobral" <dcs@newsguy.com>
To:        Andrew Gallatin <gallatin@cs.duke.edu>
Cc:        freebsd-current@FreeBSD.ORG
Subject:   Re: loader question
Message-ID:  <3AD125D0.8CD47620@newsguy.com>
References:  <15056.50143.136761.578801@grasshopper.cs.duke.edu>

next in thread | previous in thread | raw e-mail | index | archive | help
Andrew Gallatin wrote:
> 
> How do you make the loader _NOT_ load a kernel until after the
> countdown?
> 
> On slow media (like NFS boots or VMware, or old AlphaServers) its
> really painful to wait for the kernel to unload just so you can unload
> it and then load an alternate kernel.

Actually, it requires some work to do that. Previously, autoboot only
loaded the kernel after the countdown, but that resulted in the small
problem in the user _not_ knowing exactly what kernel was being loaded
until after the countdown had finished.

The stuff in examples/bootforth does something similar with the menu.
The menu waits until you type a key or up to a certain amount of time,
and then go do whatever it is that was selected/is default. You can look
there for an example and adapt it to suit your needs, but Forth code is
not particularly easy to understand, even something as simples as that.
Of course, since you _are_ that far from the machine, I'd recommend
testing anything locally first.

-- 
Daniel C. Sobral			(8-DCS)
dcs@newsguy.com
dcs@freebsd.org
capo@the.secret.bsdconspiracy.net

	all your kernels arpanic: blockable sleep lock (sleep mutex) Giant @
../../kern/kern_sig.c:153

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3AD125D0.8CD47620>