#Km91#Live Dangerously
cygnusI use Arch BTW full-time for work and personal for about 3 years now and haven’t had any issues at all.
FunkyCheeseI worked with someone who uses arch on his work laptop
One day it just died and he had to spend a day or two setting it all up again
I mean, its not common, but it happens
Yeah, I ran arch through college, it broke 3 times over 4 years, basically each time because Nvidia updated. Now that I don’t have the time to fuss with spending a couple of hours chrooting in and fixing Nvidia stuff, I just swapped to endeavorOS sway community edition (and made sure none of my PCs have Nvidia anything in them) and haven’t had an issue yet.
Yep, the only time things have broken in Arch for me has been with Nvidia driver updates.
Yep. Funnily enough, never really had any issues with the drivers on a desktop, only on mobile, mostly switching between integrated and discrete. But after messing with them on my laptop for a few years, you better bet my laptop was only running Intel integrated and my desktop runs on amd.
antsuI’d guess that keeping configs in Ansible would reduce that setup time to an hour or two.
flying_sheepThat doesn’t happen. When it breaks, it’s always recoverable, and it very very very rarely breaks (>10 years Arch user here, never lost sleep about it)
I’ve been dailying the exact same arch installation since 2014 without reinstalling it a single time.
Now to be fair I did have it non-bootable at several points. Worst of which was a PAM update which broke it completely because the new config was in a .pacnew file and the old one was not compatible anymore. But since it was a edge-case there was no forum post about it. Still recovered it just fine after an hour or so of troubleshooting.
It’s all open-source and usually decently documented. The only reason anyone should have to reinstall a Linux desktop is lack of experience, but I would always advise to persevere because troubleshooting my system is how I gained much of my expertise. If that’s not what you want, stick to Debian.
The only issue I ever had was Arch ARM changing the naming convention for network devices and making me have to plug the first Raspberry Pi that I upgraded into a monitor to debug what was going on.
This was annoying for sure, but less annoying than using a 6 year old Python version like the Red Hat Enterprise Linux at work…
StarDreamerI see your 6 year old python version and raise you RHEL5 running python 2.5 in 2022.
That thing didn’t even have a base Exception class.
paequ2Yeah, people like to think that bleeding edge means “untested”. As if your OS was directly receiving the dev’s
git push…
swab148I wonder if there’s a package manager that does just that, I want the real bleeding edge!
IllecorsAround 10 years here. Some issues, but much less time wasted in total than if I had done “dist-upgrade”s the whole time.
festntIt’s what Debian and similar distributions use to switch from one stable release to the next. This happens every half year for Ubuntu and every blue moon for Debian, which makes it a significantly more error-prone process than updating Arch every week in my experience.
The LTS released every other year) is supported 5 years.
Oof, that’s probably almost a full reinstall when you upgrade, depending on how stable your stack is. A lot of services will will have breaking config changes in that time frame.
One huge advantage of a rolling distro is that generally only one thing can break at a time :)