On the opposite end here. I know if there’s a kernel update then I’d need to reboot and restart everything.
Only to activate the new kernel! You can just leave the current one running with minimal issues, even less if you have something like KernelCare live patching security bugs
Assuming any dynamically loaded module will fail, why does KernelCare exist and why is it used so prevalently in web hosting environments? It costs money, so buying it when it doesn’t work seems odd.
I unironically do that
$ pacman -Syu
$ sudo !!
Sudo Pac-Man -Sy
Is there a safe way to do uodates automatically? I could store my password in plaintext and thats barbaric but it still doesnt fix the problem that packages and dependecies can break during updtaes without user input if im right. Tho i guess you could write a script that automatically looks for updates and notifies the user.
You can set up a Cron job or systemd timer for the root account to run that command regularly, if it is a non-interactive command!
I’ve never had to interact with system updates in Linux distros beyond saying “yes I want to update” in the last decade. If I didn’t want to, there’s usually a force update flag available to skip the asking part. Would I do this for a server without backups? Absolutely not. For home use? I’ll roll the dice; I have backups even if there’s a couple days of shipping time to get all 12TB mailed to me.
Of course, major distribution releases are a different monster. Fortunately, I don’t deal with those often and when I do, I migrate instead of upgrade.