this post was submitted on 10 Oct 2025
276 points (97.9% liked)
memes
17730 readers
2586 users here now
Community rules
1. Be civil
No trolling, bigotry or other insulting / annoying behaviour
2. No politics
This is non-politics community. For political memes please go to !politicalmemes@lemmy.world
3. No recent reposts
Check for reposts when posting a meme, you can only repost after 1 month
4. No bots
No bots without the express approval of the mods or the admins
5. No Spam/Ads/AI Slop
No advertisements or spam. This is an instance rule and the only way to live. We also consider AI slop to be spam in this community and is subject to removal.
A collection of some classic Lemmy memes for your enjoyment
Sister communities
- !tenforward@lemmy.world : Star Trek memes, chat and shitposts
- !lemmyshitpost@lemmy.world : Lemmy Shitposts, anything and everything goes.
- !linuxmemes@lemmy.world : Linux themed memes
- !comicstrips@lemmy.world : for those who love comic stories.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Oops, something went wrong.
Rolling back updates...
I mean, that's the preferable way should OS should handle a borked update, it sure beats just bricking the computer.
Beating turning the computer into a brick does not make it "the preferable way" to do it.
Update fails, OS rolls back failed changes. What would you prefer it to do?
Boot into terminal and leave you staring at an empty prompt
So in the event of a failed update, what would be the preferable way to handle it then? I think automatically rolling back to a functional state before the update is pretty optimal.
force shuts down computer to break windows
Install linux now.