Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
sudo in Windows.Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
Huh. Only 11 days on the Raspberry Pi I'm using as a "desktop system" right now. (Arch Linux Arm, btw... though Arch Linux Arm sucks now-a-days.)
Let's check my RPi-based NAS:
[tootsweet@mynasserver ~]$ uptime
19:56:07 up 212 days, 18:43, 4 users, load average: 0.16, 0.04, 0.01
Also not as long as I'd have guessed.
Interesting. LMDE seems to be more like MS Windows in that things like kernel updates insist on a reboot, and certain other things are easiest restarted with a reboot too, for example, X.Org changes.
I'm sure there's still a way to bootstrap a new kernel on the bare metal without needing to reboot, likewise for restarting X.Org, but I foresee problems with any programs and daemons that were children of the original processes. For example, convincing them not to exit when their parent does and then getting them to play nice under a new session.
I mean, I guess you could just not update, or have a long period where they're unnecessary and that'd work too. That could well be what this meme is getting at. Can confirm sessions (caveat: with standby and hibernate) that have lasted well over a month.
But this all raises the question: Does anyone actually not reboot when system changes happen, and what's the workflow for bootstrapping without rebooting there?