On 2026-03-20, 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.

[ Bastian Blank ]
* Split kernel modules into own package.
* Move kernel binary into own package.

So it seems to be about the udebs used during installation when size is important. It seems to be more important for linux-modules. linux-base is perhaps a step further.
https://d-i.debian.org/doc/internals/ch03.html

--- PyGate Linux v1.5.13
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On Sat, 21 Mar 2026 at 09:06, Michel Verdier <listes@verdier.eu> wrote:

On 2026-03-20, 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.

[ Bastian Blank ]
* Split kernel modules into own package.
* Move kernel binary into own package.

Hi, would you mind to explain to us where to find and
read "the changelog" that you quote above?

--- PyGate Linux v1.5.13
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On 2026-03-21, David 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.

[ Bastian Blank ]
* Split kernel modules into own package.
* Move kernel binary into own package.

Hi, would you mind to explain to us where to find and
read "the changelog" that you quote above?

I search linux-image package https://packages.debian.org/search?suite=forky&searchon=names&keywords=linux-image-6.19

You can find the changelog link on the right of the page https://packages.debian.org/forky/linux-image-6.19.8+deb14-amd64

I search "binary" in the changelog https://metadata.ftp-master.debian.org/changelogs//main/l/linux-signed-amd64/linux-signed-amd64_6.19.8+1_changelog

But looking further I found that linux-image is still where it has to be https://packages.debian.org/forky/linux-image-6.19.8+deb14-amd64

So linux-{base,binary,modules} seem to be a replacement of kernel-image
which is only for installation https://packages.debian.org/trixie/kernel-image-6.12.73+deb13-amd64-di
Perhaps they will replace linux-image in the future.

--- PyGate Linux v1.5.13
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

Michel Verdier <listes@verdier.eu> wrote on 21/03/2026 at 15:10:07+0100:

On 2026-03-21, David 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.

[ Bastian Blank ]
* Split kernel modules into own package.
* Move kernel binary into own package.

Hi, would you mind to explain to us where to find and
read "the changelog" that you quote above?

I search linux-image package https://packages.debian.org/search?suite=forky&searchon=names&keywords=linux-image-6.19

You can find the changelog link on the right of the page https://packages.debian.org/forky/linux-image-6.19.8+deb14-amd64

I search "binary" in the changelog https://metadata.ftp-master.debian.org/changelogs//main/l/linux-signed-amd64/linux-signed-amd64_6.19.8+1_changelog

But looking further I found that linux-image is still where it has to be https://packages.debian.org/forky/linux-image-6.19.8+deb14-amd64

So linux-{base,binary,modules} seem to be a replacement of kernel-image
which is only for installation https://packages.debian.org/trixie/kernel-image-6.12.73+deb13-amd64-di Perhaps they will replace linux-image in the future.

In general, tracker.debian.org is a nice resource, too.
Bests,
--
PEB


--- PyGate Linux v1.5.13
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

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.
IIUC these are special packages used only in debian-installer?

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?


=== Stefan

--- PyGate Linux v1.5.13
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On Sat, Mar 21, 2026 at 21:28:44 -0400, Stefan Monnier wrote:

`aptitude` doesn't seem to find any "kernel-image" packages.
IIUC these are special packages used only in debian-installer?

They seem to be something from unstable and testing. See for
example <https://packages.debian.org/forky/linux-binary-6.19.8+deb14-amd64>.

I wish people who are running unstable or testing would *say* so when
posting questions here. It would prevent so much confusion.

--- PyGate Linux v1.5.13
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

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.

--- PyGate Linux v1.5.13
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On 2026-03-21, Stefan Monnier wrote:

`aptitude` doesn't seem to find any "kernel-image" packages.
IIUC these are special packages used only in debian-installer?

yes it is https://packages.debian.org/search?suite=trixie&arch=any&searchon=names&keywords=kernel-image

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`?

Perhaps it will be but for now the split is only for the installer

--- PyGate Linux v1.5.13
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

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.

If you look at https://packages.debian.org/trixie/kernel-image you'll
see that while `kernel-image` is a virtual package, there are real
packages whose name starts with "kernel-image",
so `aptitude search kernel-image` should have found them, tho apparently
the fact that they're "DI only" makes them not show up somehow.

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`?

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.

I don't need that: I had already done `dpkg -L` on those new packages to
see their content. But their contents only tell me "the sum is the same
as the previous big package" but doesn't say why the big package
was split.


=== Stefan

--- PyGate Linux v1.5.13
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

Michel Verdier [2026-03-22 10:24:54] wrote:

On 2026-03-21, Stefan Monnier wrote:

`aptitude` doesn't seem to find any "kernel-image" packages.
IIUC these are special packages used only in debian-installer?

yes it is https://packages.debian.org/search?suite=trixie&arch=any&searchon=names&keywords=kernel-image

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`?

Perhaps it will be but for now the split is only for the installer.

I think the future already happened in testing&sid.


=== Stefan

--- PyGate Linux v1.5.13
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On Sun 22 Mar 2026 at 22:23:02 (-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.

If you look at https://packages.debian.org/trixie/kernel-image you'll
see that while `kernel-image` is a virtual package, there are real
packages whose name starts with "kernel-image",
so `aptitude search kernel-image` should have found them, tho apparently
the fact that they're "DI only" makes them not show up somehow.

Isn't it because they're udebs? The only thing aptitude could do with
them if it could find them is wreck your system.

I think we've been here before:

https://lists.debian.org/debian-user/2026/03/msg00011.html

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`?

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.

I don't need that: I had already done `dpkg -L` on those new packages to
see their content. But their contents only tell me "the sum is the same
as the previous big package" but doesn't say why the big package
was split.

Follow the reference in my previous post above, and:

Kernel image and kernel module udebs

Kernel udebs are built basically by repackaging a regular kernel
image package. Reason is again to reduce memory usage: not all
modules included in a kernel image package are needed during an
installation. Also, different modules are needed in the initrd for
different installation methods, remaining modules can either be
loaded later or optionally (by manual selection or through
dependencies). The package kernel-wedge contains the toolset used
to reorganize a kernel-image package into multiple kernel (module)
udebs.

Cheers,
David.

--- PyGate Linux v1.5.13
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On 2026-03-22, Stefan Monnier wrote:

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`?

Perhaps it will be but for now the split is only for the installer.

I think the future already happened in testing&sid.

Yes you're right. I don't check before but in forky linux-image is now an
empty package with dep to binary+modules+base https://packages.debian.org/forky/linux-image-6.19.8+deb14-amd64

--- PyGate Linux v1.5.13
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)