Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 25 Apr 2014 14:58:34 -0700
From:      Nathan Whitehorn <nwhitehorn@freebsd.org>
To:        Glen Barber <gjb@freebsd.org>
Cc:        svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org
Subject:   Re: svn commit: r264935 - head/release/amd64
Message-ID:  <535ADA8A.4030408@freebsd.org>
In-Reply-To: <20140425215248.GB1231@glenbarber.us>
References:  <201404252111.s3PLB00Q043705@svn.freebsd.org> <535AD685.90606@freebsd.org> <20140425214454.GA1231@glenbarber.us> <535AD7C6.9030802@freebsd.org> <20140425215248.GB1231@glenbarber.us>

next in thread | previous in thread | raw e-mail | index | archive | help

On 04/25/14 14:52, Glen Barber wrote:
> On Fri, Apr 25, 2014 at 02:46:46PM -0700, Nathan Whitehorn wrote:
>> I appreciate the caution. Thanks for the clarification! I'm planning to get
>> EFI support into the installer this weekend.
> Speaking of the installer...
>
> How difficult would it be to be able to select a kernel for installation
> if more than one kernel.${foo}.txz is provided on the install medium?
>
> The use case I have in mind is where kernel.VT.txz is extracted to
> /boot/kernel.VT (which I believe the loader menu already supports
> multi-kernel), an alternate kernel can be chosen for booting and then
> can subsequently be chosen as the installed kernel during the extract
> phase.
>
> This would actually cut down quite a bit on snapshot build times, since
> right now I have to do a separate build for each kernel.
>
> Thoughts?
>
> Glen
>

Not that hard. If you want to just add extra optional kernels, the 
installer doesn't even need any patches -- you just have to add it to 
the make release logic (and MANIFEST) as an extra tarball. Installing it 
to /boot/kernel would require removing the logic in 
bsdinstall/scripts/auto that removes "kernel" from the menu as a 
nonoptional package.
-Nathan



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?535ADA8A.4030408>