Date: Mon, 9 May 2016 11:46:02 -0700 From: Freddie Cash <fjwcash@gmail.com> To: Ultima <ultima1252@gmail.com> Cc: John Baldwin <jhb@freebsd.org>, FreeBSD-Current <freebsd-current@freebsd.org> Subject: Re: NO_INSTALLEXTRAKERNELS and PkgBase Message-ID: <CAOjFWZ5Q2AtfvB_=EnEJ3-hzajpJGHnPWm0mnvYoBw6sKUiH_Q@mail.gmail.com> In-Reply-To: <CANJ8om4N0zoKR8ECsFDZTpaQpiBE1YoO1oMr_=H5o5Fy3Vbjhw@mail.gmail.com> References: <CAOc73CC6WoFHPDBa6LGMyhmnA1ZjiemffyTJBGBNSZwPOu8KzA@mail.gmail.com> <CAOc73CD_0O2bBNB9UH7JhzaCBj1iVD0t_FjkuPJEbWj3M2-oPA@mail.gmail.com> <20160507135005.GN62286@albert.catwhisker.org> <3382220.3AgOZzUBmF@ralph.baldwin.cx> <CANJ8om4N0zoKR8ECsFDZTpaQpiBE1YoO1oMr_=H5o5Fy3Vbjhw@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
On Mon, May 9, 2016 at 11:40 AM, Ultima <ultima1252@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. ;) -- Freddie Cash fjwcash@gmail.comhelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOjFWZ5Q2AtfvB_=EnEJ3-hzajpJGHnPWm0mnvYoBw6sKUiH_Q>