On Sat 21 Mar 2026 at 21:28:44 (-0400), Stefan Monnier wrote: > >> I recently noticed that kernel packages are now split into three > >> subpackages (linux-base-VERSION, linux-binary-VERSION, > >> linux-modules-VERSION). > >> > >> Does anyone know why this is? I'm trying to imagine scenarios where > >> that could be an advantage, but I'm coming up short. > > > >>From the changelog > > > > [ Bastian Blank ] > > * Introduce a base package for udebs as well: > > - Introduct linux-base. > > - Rename kernel-image to linux-binary. > > `aptitude` doesn't seem to find any "kernel-image" packages.
Presumably because it's the name of a virtual package. > IIUC these are special packages used only in debian-installer? I think that's been suggested. > And also IIUC the main benefit of the split is to merge the > `linux-binary` part of the old `linux-image` with the old > `kernel-image`? > > Do I understand it right? If you look at the page I referenced earlier, you can rightclick on its companion package's name and get to: https://packages.debian.org/forky/linux-base-6.19.8+deb14-amd64 in another tab. Then click on "list of files" on each of those pages and look at the lists. -binary contains the kernel binary, and -base contains the System.map and config. I would surmise that there's a -modules package hanging around somewhere that contains the modules, and the three packages sum to the old linux-image. I'm just making this up from what I see. Note to Greg: both my emails contain "forky" (as well as two foxy typos because my fingers are still learning to type the (to me) neologism). Cheers, David.
