"No way to prevent this" says only distro where this regularly happens
News from this year:
varnish, which is renamed to vinyl-cache (it's a proxy, only affects servers)Repost.
Also, my Mint install broke, uh, shit I don't remember, 5 times? Arch broke zero times. Zero times not my own fault for forgetting I was installing something and shutting off the computer, of course. Except for the times I tried the fucking installer python script, but since I never even booted the install it doesn't count.
Mint broke for you? That's the first I've heard of it.
Also if you have a habit of shutting down the PC during updates, check out atomic/immutable distros. They are almost impossible to break. You can pull the power during an update and it'll be fine.
Mint breaks weirdly often but also it's inconsistent in my experience. It's a great example of it explodes for some people and others it's a god like entity of perfection. Never in-between. Lol
Iptables change actually fucked me because I'd tweaked something stupid 12 years ago and forgot. Took lime 45-60 mins to fix
Foot-guns are my PROTECTED SECOND AMENDMENT RIGHT.
Arch explicitly says "never do this"
Well yeah and cigarettes tell you not to smoke them
Reminds me of my try of Nobara. I do clean install, it installs and starts updating itself for a long while. Afterwards it tells me to reboot, and that the update has failed. I am??? Since I am a noob, so I reboot. And the whole system fully breaks, and no trouble-shooting helps, so I have to re-install. No biggie, just mildly annoying, it was a clean install after all. Then I do some searching to figure out, what went wrong, and find out, that updates failing and the system fully breaking, and having to re-install it if you reboot, is apparently normal behavior for Nobara.
Except the last arch news post is a month ago about virtualbox. I've blindly run pacman -Syu for years without issue
It's difficult to take people shitting on arch in here seriously. I'll take 1h per year fixing whatever broke over a whole weekend upgrading Debian.
Oh and god forbid you need to compile yourself a package and maybe a few of its dependencies from scratch because that 6 years old bug didn't make it through the freeze last release.
Debian can take a week to upgrade? Apparently I’m yolo’ing it and just the upgrade. However I have just done one major update, so u might just be lucky
Whole weekend upgrading debian? I am confused. That's not how debian works?
What happened with Arch?
Wait, let me update real quick and reboot, brb
the fact that they wrote "be right back" 5 hours ago and then never came back is telling
Another 13h later, still nothing
almost 30h now, the arch update has to have bricked their hardware or something O.o
Maybe bricked the user too
Every hero has a journey.
Yours has just begun.
I warn you, this is not the easy path.
But I urge you to heed the call.
For though there will be trials and tribulations,
soon, my friend, you will own new socks.
This hasn't been a thing in years at this point
Why, what news? What I need to be careful this time?
Nothing. OP is imagining an idiot for imaginary internet points.
Idk, I've had installs of Kinoite, Bazzite, and NixOS bork themselves unrecoverably. Arch, if something goofs, more often than not I can work my way back to a working system without wiping.
i use arch btw
this happened to me once in 6 years. it was my own fault.
Why would anyone want to use a distro that can break at any update unexpectedly or have to read articles first to see if it's safe is beyond me.
It's too much of a hassle.
yeah windows do be like that
I've yet to have one of my windows systems brick itself. Several of my Linux systems have.
Any distro can break at any update. If you've ever done a major upgrade on any fixed-release distro, you have very likely experienced some sort of issue.
And the solution is very simple (and the same for all distros): Enable Snapshots, roll back if important stuff breaks.
That's literally every distro ever. Fuck even debian can break on an update. Things happen.
Really? It happens this often?
In 26 years, I've seen this happen in two occasions with enterprise Linux. One of them was my own damned fault for using a marginal config. The other was an update that added a new dependency in the code but not the package.
That's it. Twice.
Yeah i had this happen with devices that originally came with Windows sometimes, mainly laptops. It must be a combo of BIOS, firmware and hardware that increases the chances of update instability. Its just not feasible for every distro to have the same kind of hardware config testing support that Microsoft has for Windows.
Windows spying on you is not just for marketing, they grab your current environment and sanitize the result so they can get a nice list of hardware and application configurations for when they need to test.
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