Date: Wed, 28 Jul 2021 17:32:03 +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: <20210728173203.GK1648@FreeBSD.org> In-Reply-To: <CAOtMX2gMFykt9RhB8ODCBfJp3KK9uJDvvXxp8PpcdF57OB=g-A@mail.gmail.com> References: <CAOtMX2jb1nEJCbo=5he5=oa1vjs_6T_BZZQfNQKVNX3AxbNCqw@mail.gmail.com> <20210728172650.GI1648@FreeBSD.org> <20210728172830.GJ1648@FreeBSD.org> <CAOtMX2gMFykt9RhB8ODCBfJp3KK9uJDvvXxp8PpcdF57OB=g-A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--FnOKg9Ah4tDwTfQS Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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 them > > all in > > > > a release image? release.conf says so. But from experiment, what I > > see is > > > > that: > > > > > > > > * release.sh does pass both kernels in the KERNCONF variable to "ma= ke > > > > buildkernel" > > > > * "make buildkernel" dutifully builds both > > > > * BUT, "make installkernel" only installs the first kernel and igno= res > > the > > > > rest > > > > * Only the first kernel ends up in the final image > > > > * It's not really clear where an alternate kernel should go, anyway. > > > > Probably someplace like /boot/kernel.debug , but release.conf doesn= '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/7045b1603bdf054145dd958a4ac= c17b410fb62a0/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". It is, I just want to make sure I'm looking in the right place(s). Glen --FnOKg9Ah4tDwTfQS Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEjRJAPC5sqwhs9k2jAxRYpUeP4pMFAmEBlJMACgkQAxRYpUeP 4pNRvhAAgpfnbJCPmBn1PzwE2hxIzG7iGpSfqjN2oQp8QZiY+Ce5YZUD6ZK7R7o8 J9fcnU2e4Mkstflh+h6ckeA+Px2U6cx2x7a0aOKB6Dof+5g0NyHNUKYVqULggQ5r m3v66+Cnj1sYNNTjSF0K60oR5ySvFpcojNi/pk8TbSWp83m0zDgZ60nlvCXGYv0t w+rn6PHkMqzuARVbz4npFlLm6hU/GUCA+zHiX5tnXnNKL4XFHT7rt64lyMhuCL5R xyVxgZn3Kse5scn3uAOaVu+s2Y0R0kO/9ClKFNc1PEw0cjIZrWt9T6GAH13A7tec kUfTP5YA1HLurEL3TYfSoaEg4g32EWq2jzjpy7LYQsELVj0+ojUv6jeAaQHlk676 V9vxPJDIIFbdm+wuLgkZ+ZaqSEACmq73XGdaCWES4fjnAA23CS08gXAB/2nozams C4a42cxmNS0ePVptiWi8w6lNBnQArhxjDc/5MCSB/qh2u69G6FgWMkVWpgc0WXFs PlhLp40+iHG9B4Puk7LcSN58Xi1Y0J4yb6E0Bw2cVpHZcwpyK7uNLJv1eoF8GFuU cDkLMX/nqqlGuZvHadutqHDxQ4iz5h8O/WGwhmUkN0iLviCIZKTVMlTALDMbaujm vg6uS12cgc2OZ3gjkz7PILTn6EpmR4Y0OFtzZ7t9ULc7L48VKJU= =qu8A -----END PGP SIGNATURE----- --FnOKg9Ah4tDwTfQS--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20210728173203.GK1648>