I'm running QubesOS, my various qubes reboot about a dozen times a day.
Have you restarted your computer this week?
251–260 of 411 posts
Re: Have you restarted your computer this week?
#252One of our customers has a daily automated restart for their servers. This is because the IT people have long lost track of what the system actually does, and feel they have no time to figure it out.
It is the bane of my existence when it comes to the predictability of uptime, not to mention long-term processes getting interrupted over the day boundary.
Re: Have you restarted your computer this week?
#253Yeah, several times. Thanks windows.
Re: Have you restarted your computer this week?
#254Earlier quoted context omitted.
Not judging, but I'm curious why you don't wear a watch?
I do typically, but I haven't always been the best at managing watch charge. It's a coros fitness watch and I've killed it on some hikes by using the GPS too much. Overall not a huge problem, but it is annoying.
There's many cheap watches with effectively infinite battery. But no gps
Re: Have you restarted your computer this week?
#255Earlier quoted context omitted.
It's more relevant on ios/Android where you can't through normal means install malware at the system level. Linux is moving in this direction with immutable OSs and better secure boot support but there isn't an easy way to have a secure linux desktop setup currently.
On phones malware is more restrained by the sandboxing. But now the reboot isn't necessary in the first place.
Exploits break out of the sandbox for higher system access. Rebooting flushes them out because the exploits have abused some memory bug to load custom code in the system, but this can not persist a reboot since everything gets cyrptographically verified on boot.
This is why things like the Nintendo Switch hacks and iphone jailbreaks have to be reloaded every time the system reboots, while they could modify the system files to try to persist the malicious code, it would simply leave the device unbootable since the boot chain attestation process would refuse to boot when the checksum doesn't match. The malware can only come back when the initial bug has been triggered again, through receiving a malicious text message attachment for example.
Re: Have you restarted your computer this week?
#256I 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!
I remember installing some new computers for a small shop around y2k, and their NT4 server was acting up a bit when I was adding the new users to the domain controller.
I opened Task Manager to see if any processes was running wild. Imagine my surprise when I saw it had well over 1100 days of uptime!
Re: Have you restarted your computer this week?
#257Earlier quoted context omitted.
It relies on your software to be properly sandboxed and permissioned. What we have seen is state funded hacking groups can often exploit bugs which break out of sandboxes and embed themselves in the system. But the malicious code only exists in memory, it can’t persist between reboots because the next boot would fail the checksum and signature checks. Which is why security focused OSs will periodically reboot themsel…
> It relies on your software to be properly sandboxed and permissioned. And organizations rely on their employees not falling for phishing email. How well has that worked? > What we have seen is state funded hacking groups can often exploit bugs which break out of sandboxes and embed themselves in the system. But the malicious code only exists in memory, it can’t persist between reboots because the next boot would fa…
This is true, which is why it's extremely hard to create a secure linux desktop today. But things are moving in the right direction, if you use Wayland + Flatpak on a immutable OS with secureboot set up you are in a much better position than a standard distro.
Re: Have you restarted your computer this week?
#258Earlier quoted context omitted.
As a Linux user, it pisses me off whenever I am forced to reboot, and I'm very disappointed if my laptop uptime is measured in less than months. Needing to shut down to me indicates something is broken.
What can possibly require a laptop to be up for months? I have a Linux server that can run for years without needing a reboot. But my laptop I just shut it down after my work is done
What can possibly require a laptop to be shut down instead of put to sleep?
Re: Have you restarted your computer this week?
#259When you use disk encryption for security reasons it seems to me you need to turn off your computer after your done.
Re: Have you restarted your computer this week?
#260Have you ever lost a laptop, through theft or coffee spill or mainboard failure or just accidentally wiping something?
I have three machines now: two laptops that syncthing to a mini pc that sends snapshots offsite. Losing access to one laptop is no longer a day-ending, world-stopping event!
As such, the safest ground state for any machine is to be sync’d then powered off. I do it after every “session”: before lunch, at the end of the day, and often in between if I’m at home and just using the machine for 45 minutes to e.g. buy a mattress before going back to the garden.
Similarly, with my work machine, I push everything to the central repository at the end of every day and delete all my local branches. They are more prudent with spending so I don’t have a hot-spare second machine like I do at home. The next best thing is to be prepped for catastrophic data loss at all times.
I often think about why I only have one phone. Losing that would suck but it’s harder because it’s iOS and I’m less knowledgable about how to automate it as a cattle phone, not a pet phone.