Date: Mon, 15 Jul 2024 16:05:44 -0600 From: Warner Losh <imp@bsdimp.com> To: Colin Percival <cperciva@freebsd.org> Cc: Tomoaki AOKI <junchoon@dec.sakura.ne.jp>, Peter <pmc@citylink.dinoex.sub.org>, freebsd-stable@freebsd.org Subject: Re: Change to FreeBSD release scheduling etc. Message-ID: <CANCZdfqVyj6mkLdkTKqKwK=8_7ugJ6esLj=ZkaHXOsU6UwVMeA@mail.gmail.com> In-Reply-To: <0fb67778-d279-420b-b482-5ce36e08a1be@freebsd.org> References: <ZpPCADUpmCFHNa49@disp.intra.daemon.contact> <3598c6db-6d8a-4efa-b5fc-1fc697608860@freebsd.org> <20240716063356.f0993ae6f7648ae19c1ae33f@dec.sakura.ne.jp> <0fb67778-d279-420b-b482-5ce36e08a1be@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--000000000000e2a936061d506e76 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, Jul 15, 2024 at 3:57=E2=80=AFPM Colin Percival <cperciva@freebsd.or= g> wrote: > On 7/15/24 14:33, Tomoaki AOKI wrote: > > On Mon, 15 Jul 2024 11:58:16 -0700 > > Colin Percival <cperciva@freebsd.org> wrote: > >> Extending the minor-release support period might be possible, but that > >> would depend on portmgr and secteam and I can't speak for them. One > issue > >> which would certainly come up is kernel module packages -- our package= s > >> are built for each stable branch on the oldest currently supported > release, > >> which means that e.g. new features in 14.1 can't be used until 14.0 is > EoL; > >> this is a problem particularly for graphics drivers. > > > > How do you think about flavorizing kmod ports in kmod.mk and provide > > pkgs for latest patch release (like 14.0-p8) of all supported > > point releases (like 14.0) [1]? > > Does it look possible and feasible? > > Rebuilding kernel modules for each patch level shouldn't be necessary. I= f > we break KBI in a security or errata update, something has gone > astonishingly > wrong. > > Flavouring kernel module ports for each minor release -- possibly buildin= g > in > in an oldest-supported-release jail but with the relevant /usr/src/sys > tree -- > might work well? But that's a question for portmgr; I don't know enough > about > how package building works to know how feasible this would be. > People have talked about "stacking" repos to accomplish this. We'd build per-minor release images for .ko's. I'm not sure what the sticking points are for doing this, though. Ideally, we'd keep the same KBI per major release, but that ideal has falle= n short. Warner --000000000000e2a936061d506e76 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">= <div dir=3D"ltr" class=3D"gmail_attr">On Mon, Jul 15, 2024 at 3:57=E2=80=AF= PM Colin Percival <<a href=3D"mailto:cperciva@freebsd.org">cperciva@free= bsd.org</a>> wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"= margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-lef= t:1ex">On 7/15/24 14:33, Tomoaki AOKI wrote:<br> > On Mon, 15 Jul 2024 11:58:16 -0700<br> > Colin Percival <<a href=3D"mailto:cperciva@freebsd.org" target=3D"_= blank">cperciva@freebsd.org</a>> wrote:<br> >> Extending the minor-release support period might be possible, but = that<br> >> would depend on portmgr and secteam and I can't speak for them= .=C2=A0 One issue<br> >> which would certainly come up is kernel module packages -- our pac= kages<br> >> are built for each stable branch on the oldest currently supported= release,<br> >> which means that e.g. new features in 14.1 can't be used until= 14.0 is EoL;<br> >> this is a problem particularly for graphics drivers.<br> > <br> > How do you think about flavorizing kmod ports in <a href=3D"http://kmo= d.mk" rel=3D"noreferrer" target=3D"_blank">kmod.mk</a> and provide<br> > pkgs for latest patch release (like 14.0-p8) of all supported<br> > point releases (like 14.0) [1]?<br> > Does it look possible and feasible?<br> <br> Rebuilding kernel modules for each patch level shouldn't be necessary.= =C2=A0 If<br> we break KBI in a security or errata update, something has gone astonishing= ly<br> wrong.<br> <br> Flavouring kernel module ports for each minor release -- possibly building = in<br> in an oldest-supported-release jail but with the relevant /usr/src/sys tree= --<br> might work well?=C2=A0 But that's a question for portmgr; I don't k= now enough about<br> how package building works to know how feasible this would be.<br></blockqu= ote><div><br></div><div>People have talked about "stacking" repos= to accomplish this. We'd build per-minor</div><div>release images for = .ko's. I'm not sure what the sticking points are for doing this,</d= iv><div>though.</div><div><br></div><div>Ideally, we'd keep the same KB= I per major release, but that ideal has fallen</div><div>short.</div><div><= br></div><div>Warner=C2=A0</div></div></div> --000000000000e2a936061d506e76--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfqVyj6mkLdkTKqKwK=8_7ugJ6esLj=ZkaHXOsU6UwVMeA>