this post was submitted on 30 Oct 2023
1149 points (84.5% liked)
linuxmemes
21225 readers
37 users here now
Hint: :q!
Sister communities:
- LemmyMemes: Memes
- LemmyShitpost: Anything and everything goes.
- RISA: Star Trek memes and shitposts
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack members of the community for any reason.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudoin Windows. - No porn. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
Please report posts and comments that break these rules!
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
Time to update the meme.
I haven't had to touch xorg.conf in many years
It's been so long since X broke that most people won't know what you mean by xorg.conf
Hey, now with Wayland we get whole new things to fix when they break.
what the hell that exists?
I’ve had some programs break because their dependencies updated before them but never the graphics
Nvidia thing probably
You can pause and schedule update on Windows
But you can't decline them or postpone indefinitely. It'll eventually force you to restart and update, and that's a problem.
When updates break a piece of critical software and can't be postponed indefinitely it's a real problem.
I've also run into instances where my PC was performing a task that required several weeks of processing time and Windows forced a restart because the process time was longer than the postponement window, so a task that's supposed to take 3 weeks suddenly takes 6 weeks.
Yes, security is important, but sometimes it's secondary to the entire fucking reason a computer has been deployed, and Microsoft shouldn't be dictating my priorities.
You can decline them semi permanently. Mine will ask again in the year 2077.
I forget the specifics, because I've had autoupdates turned off for a while now, but I think it would make you set "active hours" and then would do updates outside of your active hours. Regardless of you actually using your computer at the time. And, back in the day, my sleep schedule was non-existent, so there was no time that was completely safe for doing updates.
There was a time when you could postpone, but they got rid of that, or limited it... eventually you'd end up with an unstoppable update. It seems microsoft is trying tons of things to get people to stay up to date, but none are satisfying to everyone.
I prefer my method, which isn't easily accessible to all, manually updating periodically. Sometimes I'm a month or 2 late, but the worst of the worst vulnerabilities ends up news and that'll get me to update sooner.
I do not think that any solution will satisfy everyone. the limit of 35 days is probably a bit short.