Date: Wed, 20 Jun 2018 20:47:40 +0200 From: Polytropon <freebsd@edvax.de> To: Mark Saad <nonesuch@longcount.org> Cc: "Igor V. Ruzanov" <igorr@pochta-mx.canmos.ru>, freebsd-questions@freebsd.org Subject: Re: Refresh my memory make release with a custom kernel Message-ID: <20180620204740.5de3d872.freebsd@edvax.de> In-Reply-To: <CAMXt9NbLGy-w4hwN-TTytmid7Li8fwaujA2aJexyD%2BJVP9B4GA@mail.gmail.com> References: <1DD85328-F718-4569-9BE8-811D34CBD779@longcount.org> <alpine.BSF.2.00.1806201607160.33412@pochta.canmos.ru> <CAMXt9NbLGy-w4hwN-TTytmid7Li8fwaujA2aJexyD%2BJVP9B4GA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 20 Jun 2018 13:26:34 -0400, Mark Saad wrote: > Igor > That did not work, the resulting kernel was still a GENERIC . For a > work around > I am just going to tar up /boot/kernel into my own kernel.txz. This is > on 11.2-SATBLE/PRERELEASE >From what I understood from the Makefiles, "make release" will always build with the GENERIC kernel configuration. There are basically two possibilities: a) overwrite GENERIC with your own configuration, or b) previously run "make buildkernel KERNCONF=<name>", tar the result from /usr/obj, then build the release, and finally replace its GENERIC objects with your own ones. See "man 7 release" for details. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180620204740.5de3d872.freebsd>