131–140 of 411 posts
Earlier quoted context omitted.
>can't get struck by lightning or surges if the surge-strip is flipped off That's not how electricity works. Hot may be open but your ground and return is not.
that's an interesting thought but would violate physics for lightning to come in through the ground line?
I need to reboot
A couple of years ago I noticed that my mac starts collecting weird little bugs if I don’t reboot for a really long time. The cursor starts misbehaving (it won’t reliably change over links, or in graphic editors), switching between apps might take a few seconds, and once I had my keyboard input latency increased by ~500-700ms for every keystroke. These issues go away on reboot. I’m trying rebooting once a week or so…
This lasted many years, across multiple apple laptops, across multiple different OS versions, across multiple different Corporate management solutions!
Mac users, like Linux users, refuse to acknowledge that it can be possible for there to be a problem that they have not personally experienced. They never extend this doubt to problems on Windows.
This is why everyone believes Apple hardware is always flawless despite nearly every machine having serious design issues that hamper or even break the machine, like a display cable getting changed to be too short in a design update such that after a while your display goes really wonky in a way that is really difficult to google, such that your IT department wont figure out that it's a known and unfixed design fault, and spend weeks trying to reinstall the OS and other troubleshooting steps.
I remember when Linux users were practically obsessive about uptime and restarting felt like a sign of failure. This was at a time when Windows seemingly needed to restart once or twice a day, at least. These days I like to turn my work Mac off at the end of the week just so I feel a literal sense of closure. It's not really the applications minimizing and running in the background; it's ME.
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!
8:59PM up 1858 days, 22:51, 1 user, load averages: 1.69, 2.21, 1.60
dblrabbit@cookie:~ $ uname -a
FreeBSD cookie.server 12.2-BETA1 FreeBSD 12.2-BETA1 r365618 GENERIC amd64
9:05PM up 1859 days, 13 mins, 1 user, load averages: 1.19, 1.32, 1.39
dblrabbit@mookie:~ $ uname -a
FreeBSD mookie.server 12.2-BETA1 FreeBSD 12.2-BETA1 r365618 GENERIC amd64
9:14PM up 245 days, 8:46, 1 user, load averages: 1.26, 0.97, 0.91
dblrabbit@dragoness:~ $ uname -a
FreeBSD dragoness 16.0-CURRENT
5years; I'm 37 now, I was 32. Life seemed easier then.
I have a cron job which restarts my computer every day (Linux Mint Debian edition). I like waking up to a "fresh" computer, and since I know that it will restart every day - this is a "forcing function" to (1) be diligent about saving things that are important, (2) treating browser tabs, random notes, etc as ephemeral, and bookmarking the important stuff. I used to work at an office where we pair-programmed with clie…
A slightly more fun version: 0 0 * * * sleep $((RANDOM % 86400)) && /usr/sbin/shutdown -r +5 "Rebooting in 5 minutes. Run 'shutdown -c' to cancel"
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 why hasn't this problem been tackled I wonder?
Wouldn't it be great if our systems could update without us having to reboot and interrupt our workloads?
This is actually useful for smartphones. Sometimes smartphone malware is capable of infecting a device but not persisting, so reboots clean it back up. At least if you trust the NSA's advice: https://s3.documentcloud.org/documents/21018353/nsa-mobile-d...
On GrapheneOS, restarting also brings the device to a BFU state, which makes it loads harder for an adversary with physical access to unlock it.
fun thing is that graphene had the feature to automatically reboot on a timer after inactivity for a while, but now ios also ships it :D
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!
8:59PM up 1858 days, 22:51, 1 user, load averages: 1.69, 2.21, 1.60 dblrabbit@cookie:~ $ uname -a FreeBSD cookie.server 12.2-BETA1 FreeBSD 12.2-BETA1 r365618 GENERIC amd64 9:05PM up 1859 days, 13 mins, 1 user, load averages: 1.19, 1.32, 1.39 dblrabbit@mookie:~ $ uname -a FreeBSD mookie.server 12.2-BETA1 FreeBSD 12.2-BETA1 r365618 GENERIC amd64 9:14PM up 245 days, 8:46, 1 user, load averages: 1.26, 0.97, 0.91 dblrabbi…