Hello mates,
As you know, in arch Linux the kernel is updated frequently but, is mandatory or good practice reboot any time the kernel is updated?
Edit: Thank you guys for your replies
deleted by creator
Except for kernel modules - which are stored on disk and often loaded on demand. Though most distros keep around the old kernel and kernel modules to avoid issues. You can still get issues on distro such as Arch which replace the kernel and modules on an upgrade - though there is the
kernel-modules-hookpackage with pacman hooks to keep the old modules around until the next reboot to fix this.If you don’t have the
kernel-modules-hookpackage installed on Arch you really should reboot shortly after an upgrade to the kernel or else new devices you plug in might not function until you do (typically USB as those tend to be what you hotplug the most).deleted by creator
First time I hear about kernel-modules-hook. For sure I’m going to try.
Thanks for the recommendation
Is this one https://archlinux.org/packages/extra/any/kernel-modules-hook/ https://github.com/saber-nyan/kernel-modules-hook ?
The Idea sounds cool, but it doesn’t seems to be maintained…
deleted by creator
Good practice, you won’t see the update until you reboot and I suppose it could cause problems if other packages were updated at the same time and rely on the updated kernel
deleted by creator
An update is only truly done once no remnants of the old code is in memory. Code can stick around in the form of binaries (restart the binaries), libraries (restart all binaries that use this library) and the kernel (reboot or use kexec).
One very simple way to make sure no old code sticks around is to reboot:-)
You don’t have to, but you could run into issues because when a kernel is updated its modules are unloaded. So, for example, you won’t be able to load external drives until you reboot or manually load the needed module.
I’ve had issues after updating the kernel and ignoring it. I WFH and all of a sudden my sound would stop working or something else may stop. I found it much easier just to reboot after.
I’ve heard about Linux servers running for years. But surely they change kernel without a reboot? More of a curious question.
there is live kernel patching, most distros (like Arch Linux) however don’t set this up by default
there is also the possibility that one live patch don’t work properly
the only reliable way currently to load the full new kernel is via rebootthe real way for server however is to not rely on one single server but have a redundant amount which you can reboot one at a time
Last time I tried replacing the kernel without a reboot it still reset the uptime. And it had about as long of a pause when replacing the kernel as a reboot had. So I don’t see the benefit.







