If this was a Linux update, which makes no sense because how can you not fully debug a 5 function clock app, it would be so inconsequential you’d never know it was patched.
MS? LETS INTERRUPT YOUR ENTIRE WORKFLOW SO THAT WE CAN PUSH 49 NEW LIBRARIES NECESSARY TO RUN OUR CLOCK APP
5 minutes later in ask lemmy, “DAE too many Linux posts?! BRB need to reboot windows for the 30th time today.”
It can’t, really. What Linux will do (and Windows won’t) is delete old files and replace them with new ones while they are still in use. But this has two problems.
It can lead to stability issues. See e.g. Firefox, which refuses to open new tabs and can’t shut down cleanly if you update using the package manager while the browser is running. If you replace a binary executable in use and it later tries to load a shared library dynamically, it will get an unexpected version of that shared library which can potentially lead to memory corruption. Similar problem if the program tries fork+exec itself to create more instances (like Firefox and Chrome do).
It won’t actually update the running process in memory, so even if you install security fixes your system will still be vulnerable. To be safe after e.g. fixes to libc you really need to reboot your system, but most distributions hide this fact from the user.
Windows could certainly opt for a similar solution as Linux. They just chose a stricter and more reliable model for file locking, for good or bad. For what it’s worth I personally prefer the Linux model, but that’s because I know to reboot my system after updating it. I don’t trust my dad to take that social responsibility so he needs to be forced.
Updating a shared library requires an understanding of which services (and interactive programs) use that shared library. There’s a lot of room for mistakes. So while restarting specific services can be worth it for a high-availability server, for a desktop PC I find it easier and less error-prone to just restart the machine. If you are really keen to avoid going into POST you can use kexec.
I work at night and Windows loves to push Windows Updates at night regardless of my normal work schedule.
Take a trip to the bathroom or just don’t move the mouse for a few minutes and Windows will reboot (fuck whatever you had running) and spent an hour or two installing an update (fuck the rest of your night)
Linux doesn’t ever try to force itself on you like that, it’s a respectable OS
Linux distros usually raises a reboot required flag. But thats usually to complete some kernel or system update. Windows just go ahead and reboot on update ruining the workflow.
When you get the message to reboot ignore it and do your work. Then shutdown after doing it. Turn on when you need it the next time. And its all well
“DAE too many Linux posts?! BRB need to reboot windows for the 30th time today.”
That’s a strawman argument, I can’t remember the last time I had to reboot Windows, and the last few updates have only taken a few minutes. They also install on shutdown most of the time.
If this was a Linux update, which makes no sense because how can you not fully debug a 5 function clock app, it would be so inconsequential you’d never know it was patched.
MS? LETS INTERRUPT YOUR ENTIRE WORKFLOW SO THAT WE CAN PUSH 49 NEW LIBRARIES NECESSARY TO RUN OUR CLOCK APP
5 minutes later in ask lemmy, “DAE too many Linux posts?! BRB need to reboot windows for the 30th time today.”
Plus Linux could update it in the background while the app is running. There’s no reason windows can’t do these things, and yet, it can’t.
It can’t, really. What Linux will do (and Windows won’t) is delete old files and replace them with new ones while they are still in use. But this has two problems.
Windows could certainly opt for a similar solution as Linux. They just chose a stricter and more reliable model for file locking, for good or bad. For what it’s worth I personally prefer the Linux model, but that’s because I know to reboot my system after updating it. I don’t trust my dad to take that social responsibility so he needs to be forced.
Outside of the kennel a reboot is not necessary you just restart the app/service it’s really not rocket science.
9.9/10 times you just need to log out and log back in.
Updating a shared library requires an understanding of which services (and interactive programs) use that shared library. There’s a lot of room for mistakes. So while restarting specific services can be worth it for a high-availability server, for a desktop PC I find it easier and less error-prone to just restart the machine. If you are really keen to avoid going into POST you can use kexec.
You’re wrong about everything
But… But… He explained in a very organized manner, so it must be true, right?
I am rubber, you are glue
So you’re a condom?
I work at night and Windows loves to push Windows Updates at night regardless of my normal work schedule.
Take a trip to the bathroom or just don’t move the mouse for a few minutes and Windows will reboot (fuck whatever you had running) and spent an hour or two installing an update (fuck the rest of your night)
Linux doesn’t ever try to force itself on you like that, it’s a respectable OS
[This comment has been deleted by an automated system]
There’s a configuration file you can edit to prevent that. The Flatpak configures this automatically for you.
Linux distros usually raises a reboot required flag. But thats usually to complete some kernel or system update. Windows just go ahead and reboot on update ruining the workflow.
When you get the message to reboot ignore it and do your work. Then shutdown after doing it. Turn on when you need it the next time. And its all well
[This comment has been deleted by an automated system]
But I think you can ignore it, the updates just will not take effect until you reboot.
Linux bros really a blight on lemmy
Microsoft is a blight on humanity.
Tell that to all the businesses running on it.
deleted by creator
That’s a strawman argument, I can’t remember the last time I had to reboot Windows, and the last few updates have only taken a few minutes. They also install on shutdown most of the time.
I use Windows on both my work and home PC. I had to reboot both twice today. I’ll probably be switching my home PC to Linux over the holiday weekend.
That would be for the best, cause it seems you aren’t really capable of using Windows properly