Date: Tue, 17 Feb 2009 13:15:19 +0200 From: Andriy Gapon <avg@icyb.net.ua> To: Nick Hibma <nick@van-laarhoven.org> Cc: freebsd-hackers@freebsd.org Subject: Re: booting/loading a tool, not kernel Message-ID: <499A9C47.4070602@icyb.net.ua> In-Reply-To: <200902171125.24160.nick@van-laarhoven.org> References: <200902171125.24160.nick@van-laarhoven.org>
next in thread | previous in thread | raw e-mail | index | archive | help
on 17/02/2009 12:25 Nick Hibma said the following: > You are aware of nextboot(8)? That you could use to specify the 'kernel' to > load on next boot. > > Also boot.config(5) might be of use. Thanks a lot, these are very useful. But I am still thinking about an interactive menu where I could e.g. press '9' to go to "Utilities" and then could select memtest86 or memtest2009 or cputest :-) >> I'd like to add an entry to my loader menu to load/execute memtest86 >> instead of a kernel. It is built as standalone ELF executable, of course. >> >> Currently I go to a loader prompt and do: >>> unload >>> load /boot/memtest86 >>> boot >> Where should I look to get this into the forth code? >> >> Suppose I want to extend this approach. >> What would be a good name for subdirectory to put such tools? >> What would be a good way to add a sub-menu for such tools? >> >> Also, my current approach means that loader still first loads a standard >> kernel and its modules and then replaces them with memetest86. How to >> get to a loader menu without pre-loading anything? > > -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?499A9C47.4070602>