this post was submitted on 07 Aug 2023
0 points (NaN% liked)

linuxmemes

21210 readers
68 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
     
    top 3 comments
    sorted by: hot top controversial new old
    [–] MildlyArdvark@feddit.dk 0 points 1 year ago (1 children)

    I never understood these. Arch has always been rock solid for me and in 10 years or so I have never had to chroot to fix an issue. The most annoying issues have been related to PGP signatures or old certificates but those have been easily fixed.

    What is it you people do to your arch installs that fucks them up so much?

    [–] einfach_orangensaft@feddit.de 0 points 1 year ago

    forcing reboot when mid update cause u think the system froze

    [–] 30p87@feddit.de 0 points 1 year ago

    The only time it broke was due to me manually (trying to) downgrade nvidia, as the current driver broke in random ways. Resulted in 10 mins of chrooting