this post was submitted on 08 Dec 2023
239 points (94.4% liked)

linuxmemes

21180 readers
799 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

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 sudo in 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
    [โ€“] [email protected] 9 points 11 months ago (1 children)

    I've used and come back to Arch for nearly 8 years now and Manjaro has always been a broken distribution and genuinely gives Arch a bad rep.

    Arch has always been a very stable daily driver for me, never breaking and never having issues with it. I'm always confused on what people are doing when they have issues with their entire distro breaking, especially since you pick all your packages and such anyways.

    [โ€“] [email protected] 3 points 11 months ago

    I've had a few breaking changes in 10 years of dailying Arch across multiple devices.

    Most egregiously one time a PAM update included a new PAM config... which got applied as .pacnew, but the new PAM config was critical and I could not login with a cryptic error message.

    That probably took me a solid hour to figure out, because config file conflicts is probably pacman's weakest point. At least apt starts conflict resolution by default.