151–160 of 411 posts
Earlier quoted context omitted.
A slightly more fun version: 0 0 * * * sleep $((RANDOM % 86400)) && /usr/sbin/shutdown -r +5 "Rebooting in 5 minutes. Run 'shutdown -c' to cancel"
Some would say "Chaotic evil". Some would say "Always be prepared!!"
Earlier quoted context omitted.
Wat? The apple silicon one on my desk restarts in under 30 seconds. Markedly faster than the Windows PC next to it
I'm glad it works for you, but I have witnessed several coworkers restart their macbooks (some M1, some M2, possibly M3) and I don't think I've ever seen a reboot shorter than about two minutes. At one instance, I rolled over to a coworker who has just rebooted theirs and had a whole 5+ minute conversation.
aren't there other old-school people like me that shut down everything at end of day and restart the next? can't be hacked if it's completely off can't get struck by lightning or surges if the surge-strip is flipped off fans and spinning drives have lifetime on motors
Then again, I primarily use a desktop, so that probably factors in.
Earlier quoted context omitted.
So I don't have to spend 10-15 minutes saving all my open files (including the scratchpad ones I haven't named) and then later reopening all my applications, recreating all of my tmux windows and panes, setting up my vim splits and tabs again, and starting all of my stopped Docker containers?
funny, decent text editors like VS Code save even the unnamed unsaved files
Is it weird that we don't have a way to update the system without rebooting by this day and age? I think there are things in Linux like live kernel patching (kexec, ksplice), but why by 2026 is this sort of architecture of live system updates not a common or included feature yet? People hate updates and having to reboot and have downtime right? Security updates to core systems are more important than ever now too. So…
You still have to reboot for things like kernel updates. As far as I'm aware, live patching the kernel is just for security issues.
My desktop is like an actual desktop. I have my tools laid out exactly how I want them for the task I'm working on. I want to come back to them in exactly the same place when I pause for the night or weekend.
I have to clean it up occasionally, to close out things that I'm no longer working on or forgot about. But I'd rather do that incrementally than all at once. Forcing a reboot is like tipping over a physical workbench with a bunch of tools and in-progress projects on it. Just awful, and often takes hours to set back to its original position (at least browser tabs restore reliably these days).
No. And in fact it annoys me greatly that our work IT department forces a reboot once a month. My desktop is like an actual desktop. I have my tools laid out exactly how I want them for the task I'm working on. I want to come back to them in exactly the same place when I pause for the night or weekend. I have to clean it up occasionally, to close out things that I'm no longer working on or forgot about. But I'd rathe…
Sadly, my computer has apparently rebooted multiple times this week. I didn't do it, but Microsoft decided it was for the best. I remember when a restart was something you were asked to consent to, and before that you had to affirmatively decide to perform an update.
Earlier quoted context omitted.
Yes, I remember feeling pride in the stability of my systems when I saw a large uptime. I had a server that had 1000 days of uptime, once. Now when I see a large uptime, I'm terrified of what security patches the kernel may be missing!
I still remember the days of servers as pets, rather than cattle, and I was harping about server uptime. A wizened server admin piped in and said he rebooted his servers once a week. Said, if you do it any less frequently, then the odds of catching an error causing change while the person who made said change (possibly himself) is still around and can remember what they did go down precipitously. So, to avoid headach…
You need to test when servers go down, and people who use them should know and understand what happens when the are off.