NO_INSTALLEXTRAKERNELS and PkgBase

Glen Barber gjb at FreeBSD.org
Mon May 9 18:50:14 UTC 2016


On Mon, May 09, 2016 at 11:46:02AM -0700, Freddie Cash wrote:
> On Mon, May 9, 2016 at 11:40 AM, Ultima <ultima1252 at gmail.com> wrote:
> 
> > If multiple kernels are being installed like this, eg KERNCONF="FOO BAR",
> > which of the two would be default during boot? FOO because it came first?
> 
> 
> Correct.  At least, that's the way it's worked in the past, and something
> I've used quite a bit on FreeBSD 7-9.  I always have GENERIC and a custom
> kernel listed in KERNCONF, with my custom kernel listed first.
> KERNCONF="FIREWALL GENERIC" for exmaple.  That way, my custom kernel is
> installed as /boot/kernel, and GENERIC is installed as
> /boot/kernel.GENERIC, which provides me with a fall-back in case I screw
> something up with my custom kernel (happens frequently).  :)
> 
> I used to do it manually using two separate installkernel steps using an
> env var to specify the installation directory (/boot/GENERIC) (forget the
> name of that var right now), but switched to using the automatic
> installation behaviour when it became available.  Simplified things a bit.
> 
> I haven't compiled a kernel on 10+ yet; hopefully the behaviour hasn't
> changed.  ;)

It has not changed, and the same behavior will be present for 11.0 in
that "whatever installkernel does, packaged base will follow the
behavior."

Glen

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-current/attachments/20160509/7afb04db/attachment.sig>


More information about the freebsd-current mailing list