[ziml77]

It's never been a great argument. Even non-atomic Linux distros have you reboot after updates. It's just the safest way to ensure that everything is running with the updated packages. You're kind of in an untested state if you have mixed versions of applications and their dependencies running.

Plus, updates aren't the only thing that require reboots. Various config changes will need a reboot or at least require you to log out and back in. Even just adding your user to a group needs you to end your session for the change to apply.

[curt15]

Isn't the point of Linux kernel live patching (kexec, ksplice) to reduce the need for rebooting after kernel updates? There's certainly a user base that still aims to maximize system uptime.

[lproven]

Yes it is, but that's for servers. This is a desktop OS.

[rascul]

> Even non-atomic Linux distros have you reboot after updates.

It depends. Some of them have smart enough tooling to let you know if an update requires a reboot.

[mixmastamyk]

User group can be updated within a terminal when needed.

[mixmastamyk]

    exec su -l $USER 

This works with fish, not sure if bash.