Date: Sat, 11 Mar 2006 16:05:50 -0700 (MST) From: "M. Warner Losh" <imp@bsdimp.com> To: scottl@samsco.org Cc: src-committers@freebsd.org, jhb@freebsd.org, cvs-src@freebsd.org, cvs-all@freebsd.org, sam@freebsd.org, des@des.no Subject: Re: cvs commit: src/release Makefile Message-ID: <20060311.160550.67882343.imp@bsdimp.com> In-Reply-To: <44119446.9070603@samsco.org> References: <200603091335.23964.jhb@freebsd.org> <86hd668wrg.fsf@xps.des.no> <44119446.9070603@samsco.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <44119446.9070603@samsco.org>
Scott Long <scottl@samsco.org> writes:
: Dag-Erling Sm=F8rgrav wrote:
: > This talk of KERNELS reminds me of a patchset I've had for quite a
: > while.
: > =
: > Currently, 'make buildkernel' builds all the kernels you list in
: > KERNCONF, but installs only one, to /boot/kernel. I've patched my
: > tree so it installs all of them into /boot/${KERN_IDENT}. The reas=
on
: > why I haven't committed this is that I want the loader to present a=
: > list of kernels at boot time, and I don't know enough Forth to
: > implement that myself.
: > =
: > Ideally, the loader would grep each kernel and display its version
: > string in the menu; and there would be an rc.d script that links
: > /boot/kernel to $(dirname $(sysctl -n kern.bootfile)) so things lik=
e
: > zsh's kldload argument completion still work.
: > =
: > DES
: =
: Dan Sobral and I have talked about exactly this in the past. What yo=
u
: want to do is merge libregex into the loader and add the calling shim=
s
: so that it can be accessd as 4th words. It's actually a lot easier t=
han
: it sounds, but I haven't had the time or motivation to try. Once tha=
t's
: done, you'll be able to easily read directories and search for name
: patterns to use.
Another option would be to place the kernel version string in its own
section that the loader could then parse out of the kernel. It would
have the added benefit that it could tell full kernels from mere
modules that way too. That does require changes to the build
infrastructure to make work, but would have a few advantages.
But whatever is easiest to implement... I think it would be a cool
feature no matter how it is implemented.
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060311.160550.67882343.imp>