svn commit: r264935 - head/release/amd64

[Nathan Whitehorn]

On 04/25/14 15:06, Glen Barber wrote:
> On Fri, Apr 25, 2014 at 02:58:34PM -0700, Nathan Whitehorn wrote:
>> 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.
> Hmm, if I remember correctly, last time I booted an installer with
> multiple kernels, there were no options for the kernel in the
> distribution menu.  Or do you mean that if it were marked as optional,
> they would appear?
>
> Anyway, the release logic already supports 'KERNCONF="GENERIC VT"'
> listing of multiple kernels, so that is not an issue.
>
> Thanks!
>
> Glen
>

They just need to be in the MANIFEST file somehow. I guess they aren't 
being added by release(7)? All the installer does is list that file -- 
and remove kernel.txz and base.txz by hand.
-Nathan