The thing isβ¦ archβ¦. You can actually fix. Most times.
Unlike the proverbial him.
(Not that you should have to.)
this post was submitted on 03 Jul 2025
72 points (97.4% liked)
linuxmemes
26006 readers
987 users here now
Hint: :q!
Sister communities:
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 users for any reason. This includes using blanket terms, like "every user of thing".
- Don't get baited into back-and-forth insults. We are not animals.
- 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.
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, no politics, no trolling or ragebaiting.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
5. π¬π§ Language/ΡΠ·ΡΠΊ/Sprache
- This is primarily an English-speaking community. π¬π§π¦πΊπΊπΈ
- Comments written in other languages are allowed.
- The substance of a post should be comprehensible for people who only speak English.
- Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
6. (NEW!) Regarding public figures
We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations. - Keep discussions polite and free of disparagement.
- We are never in possession of all of the facts. Defamatory comments will not be tolerated.
- Discussions that get too heated will be locked and offending comments removed. Β
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
founded 2 years ago
MODERATORS
Who is NixOS for?
People who have a favourite pencil.
"Linux is my personality."
Phil Connors
Highly accurate, but, even if you fix him...An update will break him, as Arch Linux moves fast as hell!
That's the neat part, if anything's broken, just update, it's probably fixed in a next version already. Then, when you find what broke on the last update, just update again, it'll be fixed by then.
not many read the arch linux news, causing such breakage to happen ._.
After a year there's only something about linux-firmware requiring manual intervention.
I thought I wasn't reading the news in correct place. Manjaro had update snapshot discussion threads, and usually there were things to fix manually. Usually just minor things.
Possibly, but in the few years I have spent with it, it has only done that once (got a kernel panic on reboot). Managed to diagnose and fix the problem in around 10 mins without the help of the internet.
That's the thing, just because there is a breakage doesn't mean there isn't a way to fix it. It just becomes a cycle of breakage and repair...Arch goes through cycles of being temporarily broken and back to working just fine. This is merely the nature of rolling release (part of the reason why I am not a rolling release distro).
Naturally, if one has the skill to fix Arch, it would be of no real concern. It might be annoying, but it seems that you can overcome those temporary disruptions caused by introduced bugs
I suppose, but again, I would hardly call it a cycle of breakages, after all, that was the one lone time anything major broke (blatant user error aside). In small cases where things do break (non-critical) it is sort of assumed that the people using arch will have a certain level of competence in diagnosing and fixing even minor issues. Though I will admit, that is partially less relevent now, with the introduction of archinstall, and distros such as EndeavourOS.
EndeavourOS, CachyOS, and archinstall do lower the barrier to entry for Arch itself, which means that there may be really fresh users (who should probably not be on Arch) using it. As wild as it sounds, those Arch and its distros get recommended to new users that aren't technically inclined.
For the seasoned Arch users, non-critical breaks don't feel as serious, since they can fix him. It's just the new users wandering in a dark place without light (a place they shouldn't be encouraged to wander, without knowledge), that these problems are serious or can be made worse by said user misunderstanding how to apply fixes. Or prevent issues in the future.
I agree that there are likely very few serious breakages not caused by a user happening on Arch, just the potential of them happening (anything made by human hands occasionally will suffer this).
Last time I saw kernel panic on Debian and that was more than a decade ago.
In my time of using Linux, to my knowledge, I can't recall a kernel panic. I've had my boot record break, graphics drivers simply not want to load (that was fixable, just annoying), or GNOME Display Manager crashout hard related to a memory leak. I use Ubuntu and Fedora KDE these days, at most there is an occasional bug that doesn't cause major issues. Just little annoyances that can be solved with an upcoming update or using the terminal.
Arch often seems to ignore the fundamental rule:
Linus is in the right. Arch developers are frequently in the wrong.