this post was submitted on 27 Jul 2023
463 points (89.4% liked)
Technology
58303 readers
21 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Comment by someone who hasn't used Windows in an age. When was the last time you rebooted because you had installed new software? When was the last time you ran random code from a forum post to make software work? Because this windows user doesn't remember ever doing that.
Literally today. Thatβs why I brought it up. I installed updates and had to reboot twice to finish the task.
Many Linux package managers themselves tell you you should reboot your system after updates, especially if the update has touched system packages. You can definitely run into problems that will leave you scratching your head if you don't.
*nix systems are not immune to needing reboots after updates. I work as an escalation engineer for an IT support firm and our support teams that do *nix updates without reboots have DEFINATELY been the cause of some hard to find issues. We'll often review environment changes first thing during an engagement only to fix the issue to find that it was from some update change 3 months ago where the team never rebooted to validate the new config was good. Not gonna argue that in general its more stable and usually requires less reboots, but its certainly not the answer to every Windows pitfall.
The only time you truly need to reboot is when you update your kernel.
The solution to this problem is live-patching. Not really a game changer with consumer electronics because they don't have to use ECC, but with servers that can take upwards of 10 minutes to reboot, it is a game changer.
We have an Ubuntu machine at work with an NVIDIA GPU we use for CUDA. Every time CUDA has an update, CUDA throws obtuse errors until reboot.
To say only kernel updates require reboot is naive.
Damn yeah I didn't think of that either. Alright, scratch what I said. The point still stands that you very rarely need to update outside of scenarios containing very critical processes such as these, those of which depend on what work you do with it.
It's been a long slow night and morning and I was half awake when I said that. Hell I'm still half awake now, just disregard anything I've said.
This isn't true, I had to reboot debian the other day to take an update to dbus which is not part of the kernel.
Seems to be sloppy engineering. We ran a huge multi site operation on Linux and did not need to.
So you never updated the kernel?
Of course, we did. Whenever there were updates. And there were no surprises because of badly initialized services.
A couple days ago, but I have a company issued remote managed windows laptop, and I get zero say in the matter.
At least once a month my system forces me to do a reboot for updates.
I can tell it to wait, but I can not tell it to stop.
Yesterday, on one of my family members computer the Laptop speakers stopped working, after an hour of clicking through legacy Ui trying to fix it(Lenovo Yoga 730 if someone could help me) I gave up, plugged my Linux boot usb in to test if there is a driver issue or so. Miss click in the boot menu and had to wait half an hour for a random Windows update(I did not start it because I used the physical button to turn it off, with Windows 11 turning off the computer via software requires so much mouse movement).