Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.kernel > #91856

Re: How is "keep two last kernels" policy implemented?

Path csiph.com!weretis.net!feeder8.news.weretis.net!news.samoylyk.net!gothmog.csi.it!bofh.it!news.nic.it!robomod
From Ben Hutchings <ben@decadent.org.uk>
Newsgroups linux.debian.kernel
Subject Re: How is "keep two last kernels" policy implemented?
Date Mon, 30 Mar 2026 16:20:01 +0200
Message-ID <MElDb-bqB8-3@gated-at.bofh.it> (permalink)
References <MD7LX-aBsW-1@gated-at.bofh.it>
X-Mailbox-Line From debian-kernel-request@lists.debian.org Mon Mar 30 14:15:47 2026
Old-Return-Path <ben@decadent.org.uk>
X-Amavis-Spam-Status No, score=-11.361 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, LDO_WHITELIST=-5, PGPSIGNATURE=-5, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SARE_MSGID_LONG40=0.637] autolearn=ham autolearn_force=no
X-Policyd-Weight using cached result; rate: -4.6
Content-Type multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="=-GPUfrvwJHHC7rRzd0Xve"
User-Agent Evolution 3.56.2-9
MIME-Version 1.0
X-Sa-Exim-Connect-IP 2a02:578:851f:1502:391e:c5f5:10e2:b9a3
X-Sa-Exim-Mail-From ben@decadent.org.uk
X-Sa-Exim-Scanned No (on maynard); SAEximRunCond expanded to false
X-Mailing-List <debian-kernel@lists.debian.org> archive/latest/154503
List-ID <debian-kernel.lists.debian.org>
List-URL <https://lists.debian.org/debian-kernel/>
List-Archive https://lists.debian.org/msgid-search/7cfabf67aee21b9e8bc64a777cd4b95e4e1ddf18.camel@decadent.org.uk
Approved robomod@news.nic.it
Lines 60
Organization linux.* mail to news gateway
Sender robomod@news.nic.it
X-Original-Date Mon, 30 Mar 2026 16:15:22 +0200
X-Original-Message-ID <7cfabf67aee21b9e8bc64a777cd4b95e4e1ddf18.camel@decadent.org.uk>
X-Original-References <85D3FD27-C6C4-459D-B3CB-0921C03618A3@gmail.com>
Xref csiph.com linux.debian.kernel:91856

Show key headers only | View raw


[Multipart message — attachments visible in raw view] - view raw

On Fri, 2026-03-27 at 06:15 +0100, Thibi wrote:
> Hello team,
> 
> I can't find any technical documentation about how Debian decides to keep two kernels, and which ones. I am particularly interested in understanding how the "manual" or "automatic" package installation flag may, or may not, influence the policy? 
> 
> Long story: something happened on my Trixie 13.4 which resulted in both current and previous kernels to become unusable. I asked apt to install the N-2 kernel and it worked, I can boot on it. Now I have:
> 
> * Kernel N (last) - automatic - broken 
> * Kernel N-1 (before last) - automatic - broken
> * Kernel N-2 - manual - working 
> 
> I wonder what will happen when a new kernel becomes available, and how I can have some influence on the automatic selection. 
> 
> Please could you point me to some documentation explaining the details? 
[...]

APT has a special case for kernel packages, which is configurable. 
Search for "kernel" on
<https://manpages.debian.org/trixie/apt/apt.conf.5.en.html>.

Ben.

-- 
Ben Hutchings
Life would be so much easier if we could look at the source code.

Back to linux.debian.kernel | Previous | NextPrevious in thread | Find similar | Unroll thread


Thread

How is "keep two last kernels" policy implemented? Thibi <thierry.bissler@gmail.com> - 2026-03-27 06:20 +0100
  Re: How is "keep two last kernels" policy implemented? Ben Hutchings <ben@decadent.org.uk> - 2026-03-30 16:20 +0200

csiph-web