Date: Wed, 28 Jul 2021 17:56:57 +0000 From: Glen Barber <gjb@freebsd.org> To: Alan Somers <asomers@freebsd.org> Cc: FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: Re: Building multiple kernels with "make release" Message-ID: <20210728175657.GL1648@FreeBSD.org> In-Reply-To: <20210728173203.GK1648@FreeBSD.org> References: <CAOtMX2jb1nEJCbo=5he5=oa1vjs_6T_BZZQfNQKVNX3AxbNCqw@mail.gmail.com> <20210728172650.GI1648@FreeBSD.org> <20210728172830.GJ1648@FreeBSD.org> <CAOtMX2gMFykt9RhB8ODCBfJp3KK9uJDvvXxp8PpcdF57OB=g-A@mail.gmail.com> <20210728173203.GK1648@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--UUMz/kfoogzZ9WLZ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jul 28, 2021 at 05:32:03PM +0000, Glen Barber wrote: > On Wed, Jul 28, 2021 at 11:30:44AM -0600, Alan Somers wrote: > > On Wed, Jul 28, 2021 at 11:28 AM Glen Barber <gjb@freebsd.org> wrote: > >=20 > > > On Wed, Jul 28, 2021 at 05:26:50PM +0000, Glen Barber wrote: > > > > On Wed, Jul 28, 2021 at 11:11:48AM -0600, Alan Somers wrote: > > > > > Is it possible to build multiple different kernels and include th= em > > > all in > > > > > a release image? release.conf says so. But from experiment, wha= t I > > > see is > > > > > that: > > > > > > > > > > * release.sh does pass both kernels in the KERNCONF variable to "= make > > > > > buildkernel" > > > > > * "make buildkernel" dutifully builds both > > > > > * BUT, "make installkernel" only installs the first kernel and ig= nores > > > the > > > > > rest > > > > > * Only the first kernel ends up in the final image > > > > > * It's not really clear where an alternate kernel should go, anyw= ay. > > > > > Probably someplace like /boot/kernel.debug , but release.conf doe= sn't > > > > > provide a way to specify that. > > > > > > > > > > So is the "multiple kernels in release.conf" feature unfinished? = If > > > so, > > > > > does anybody have a good idea about the best way to finish it? > > > > > > > > > > > > > https://github.com/freebsd/freebsd-src/blob/7045b1603bdf054145dd958a4= acc17b410fb62a0/release/release.conf.sample#L32 > > > > > > > > > > > > > Last I was aware, based on a patch sent to me privately, I believe,= it > > > > should work. > > > > > > > > Let me take a look. > > > > > > > > > > Oh, wait. Are you using 'make release' or release/release.sh? > > > > >=20 > > I'm using release.sh. I thought that was just a wrapper for "make > > release". >=20 > It is, I just want to make sure I'm looking in the right place(s). >=20 Just on a hunch, could you try with adding INSTALLKERNEL=3D"${KERNEL}" to your release.conf? I now seem to recall some weirdness with this, but the exact details elude me at the moment. Glen --UUMz/kfoogzZ9WLZ Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEjRJAPC5sqwhs9k2jAxRYpUeP4pMFAmEBmmkACgkQAxRYpUeP 4pPX2Q//btJsc7pI7M6qU9fFgyotzkrMTc5KXrJ4oLYqOasAn2FejQoubrGZd8Dd KaK11Oas1gtPqeqg2whFEgkmx1rOcnz4OkTYg560wdTQlnbT2e+Yc7YAwrtL2ytM k0veryBT8IA9r6kg036CbGHz8+TCAP2yXDIs2Ou6aUvUvQYkp0IpeFFMywIliT6R go/U8YFWLAJ3MfJ826Jz2MriPsIv167dN05zcBKiK1+ahyhMU7vWxGu5H9lT5tM0 vmyh+sdtKUa4OvI8Upcpuw2HBANhmwZTsi4A/IIfY6TT/acnEVsh4pVlyw3kf1Dn KMUK0VtNauJqGCeHtHnNXinkDnngUXvJWwTdTh06ocWT/3rdJe3WVxc54lfJRaeo P2VSDQQpfkbLkm8jDMX0ogV4JiLmwFyoAGweJBjv2TkRLWaI0YRWNFeWuZZ78Wfm 8iWBoH51py1I3BPmh+grfi5MtfKYEPgLA+lFDMHS+PFI0p6MvbiLOztc7AviYsGz 2Fio4y26b5N+R7MU9Mf5w5wzdMpQVs9fIiElouVnpkrb3Ckr/ngOU4nKZpZAQwuy gkgxhsF6LAP6ChiFJkPw7s+t4KdLSrIMjpIrRjem4nLJFds1qi8Dn7lVVhQtbJ2f E9Pk0jLmOC52b0ENLVKCukea2uE4fJ4vg53bC/47RRajWR6D1YQ= =CXCV -----END PGP SIGNATURE----- --UUMz/kfoogzZ9WLZ--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20210728175657.GL1648>