Bug 201098 - packagekernel only supports the default kernel install; being able to install multiple kernels with different names would be nice
Summary: packagekernel only supports the default kernel install; being able to install...
Status: Closed Not A Bug
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: CURRENT
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-06-24 20:33 UTC by Enji Cooper
Modified: 2015-06-24 21:06 UTC (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Enji Cooper freebsd_committer freebsd_triage 2015-06-24 20:33:25 UTC 
- packagekernel only works if INSTKERNNAME isn't specified in src.conf/make.conf
- packagekernel only works with a single KERNCONF (KERNCONF can consist of multiple values).

Please extend packagekernel to support multiple kernconfs/INSTKERNNAME so we could build release media with multiple kernels and people can select them from a list/from the bootloader.
Comment 1 Glen Barber freebsd_committer freebsd_triage 2015-06-24 20:37:22 UTC 
The 'packagekernel' target works fine, and INSTKERNNAME is not needed in src.conf or make.conf.

Try:

 # make KERNCONF="GENERIC DEBUG" packagekernel

The selection from loader(8) is orthogonal to this, as the values need to be set in loader.conf(5), which is an entirely different bug.
Comment 2 cattelan 2015-06-24 21:06:23 UTC 
One of issue that the first kernel packaged is kernel.tgz

We added a flag to force all the packaged kernels 
  .if !defined(NO_INSTALLKERNEL) 

into the path that always adds the kernel config name to the tarball.
kernel.${_kernel}.txz 

Basically so it is clear which config was used to build the kernel.