On Thu, Aug 28, 2025 at 10:40:24AM +0200, Didier Kryn wrote:

> You don't need to reboot after kernel upgrade. The new kernel is
> loaded on next reboot, but the previous one remains perfectly
> functionnal; it just lacks the latest refinement or security fix
> which you are most often not concerned with.

What about modules? Presumably if you're upgrading the kernel image
you're also upgrading the modules tree. If that actually *overwrites*
the modules tree being used by the running kernel, i.e. if the
upstream kernel version didn't change, I see potential grief when the
running kernel tries to load a module from the new tree.

One would think that distributions cover this by changing the module
tree name for every upgrade, maybe using the EXTRAVERSION tweak for
kernel builds, but this is definitely not the case for my "desktop"
(really a system76 laptop) with an ubuntu derived distribution.

I can't say how devuan handles this because on my devuan system
the VPS provider (linode) manages the monolithic kernel, separately
from apt / dpkg.

--
Ian