Debian 12 “Bookworm” was released on June 10 with a change that reaches beyond getting hardware working during installation. Official media can include non-free firmware, and the installer can configure the installed system to receive updates for the firmware it uses.
Official Debian open-use logo by Raul Silva, ©1999 Software in the Public Interest, Inc. Source and rights; CC BY-SA 3.0. Rasterized proportionally and padded; responsive adaptations use the same licence. Debian is a registered trademark of SPI. Sulat isn’t affiliated with or endorsed by Debian.
The new non-free-firmware archive component separates those files from other non-free software. For developers maintaining workstations and servers, that creates two distinct jobs: understanding what a fresh installation enables and checking the package sources of an existing system before upgrading.
Firmware access comes with an update path
The 2022 resolution behind the change allowed official installer and live images to include firmware outside the Debian system. It called for required firmware to be enabled by default, with ways to disable that behavior where possible, and for users to receive information about what had loaded.
It also addressed what happens after installation. When non-free firmware is necessary, the target system’s APT configuration should include the corresponding component so firmware can receive security updates and important fixes.
This moved into implementation before the final release. The February installer announcement describes firmware metadata, automatic component selection when non-free firmware packages are installed, and a setting to disable firmware lookup. The June release confirms that the installer may enable non-free firmware where needed.
The distinction between distribution and installation media remains important. Debian’s release notes explain that official images can combine main and non-free-firmware without including contrib or the broader non-free component. Firmware inclusion doesn’t turn those other repositories into a requirement for every installation.
An upgrade follows the existing system’s configuration
The original release announcement tells users with non-free firmware already installed to add non-free-firmware to their APT sources. A machine that obtained firmware from the old non-free component therefore needs its update configuration checked, even if the hardware already works.
The documented upgrade path is from Debian 11 “Bullseye”. The release recommends removing Bullseye backports entries before upgrading, using the bookworm-security suite and reviewing any APT pinning that could prevent packages moving to the new release.
Other changes depend on what the machine actually uses. Existing systems using systemd-resolved need the newly separate package; the announcement warns that DNS resolution may otherwise stop working. It also flags OpenLDAP configuration changes that can leave its service stopped until administrators intervene. These are service-specific migration checks, rather than evidence that every upgrade has the same failure mode.
Five years is a release commitment with package limits
Debian announces five years of combined Security and Long Term Support team coverage for Bookworm. The same release explicitly warns that some packages can’t be promised minimal backports for security issues and points readers to the release notes’ support limitations.
Those two statements belong together. The release-level support window doesn’t establish identical maintenance for every installed package. Bookworm’s firmware change follows a similar pattern: easier installation is paired with a specific repository and update mechanism, leaving the system’s component choices visible rather than collapsing them into one blanket promise.
Discover more from Sulat AI & Tech News
Subscribe to get the latest posts sent to your email.
