Le 29/08/2025 à 03:13, disparage.solvency678@??? a écrit :
> 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.

    The modules are not overwritten. They are stored under
/lib/modules, in which you can find one directory tree per kernel
version. And modutils loads the modules corresponding to the running
kernel version.

    Believe me, the people working on the Linux kernel do a serious
job; they wouldn't make such a beginners error as confusing with
incompatible versions. The package manager also does a serious job: when
you install/remove a linux-image package, it stores/removes the kernel
image, the initrd and the modules, alltogether, and all have a version
tag in some way.

    You can have several versions of the kernel installed and the Grub
bootloader allows you to choose one. It is a good practice to not remove
the previous version when intalling a new one, as a rescue in case the
new one fails to boot.

--     Didier