arch-upgrade VS kernel-modules-hook

I have the opposite feeling. Upgrading kernel requires rebooting, or kernel modules is unable to work. That's annoying. Currently I use kernel-modules-hook to prevent rebooting on Arch.

You can use this pacman hook so that old modules survive a kernel update https://github.com/saber-nyan/kernel-modules-hook

It’s a good idea to reboot ASAP after installing a kernel update anyway, but to keep things running smoothly in the meantime, I recommend installing the kernel-modules-hook package and enabling its systemd service, which keeps the current kernel’s modules available until after the next reboot. (Details here.)

Use https://github.com/saber-nyan/kernel-modules-hook to fix this. It only happens because the package manager completely removes the modules for the current kernel from the filesystem, so you can't load them anymore.

In regards to the “Core parts of the system have been upgraded, a reboot is recommended” notifications, those don’t really mean you need to reboot then. Sometimes I go through two or three minor kernel updates before rebooting my machine. You will rarely encounter things that break without a restart after “core component” updates, and if you install kernel-modules-hook from the repos, the amount of issues you’ll run into after updating will be close to zero. I’ve only encountered this kind of issue once with that package installed, and without it it’s fine too, you’ll just have to reboot if you want to do something like modprobe after a kernel update.

FWIW, kernel-modules-hook is really slow because it depends on rsync, and it rsyncs everytime the hook is fired. https://github.com/saber-nyan/kernel-modules-hook/issues/14 https://github.com/saber-nyan/kernel-modules-hook/pull/15

Thanks for this! I'll switch from kernel-modules-hook and see how it goes.

If you're talking about kernel-modules-hook, haven't you enabled the systemd service to cleanup the old modules as mentioned in the GitHub repo's README?