this post was submitted on 29 Aug 2024
655 points (98.1% liked)

linuxmemes

21222 readers
172 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
    poopsmith
    zephyr
    rtxn
    655
    Sometimes it has its own problems, but it doesn't mean that it's not great (lemmy.world)
    submitted 2 months ago by bali10050 to c/linuxmemes
    63 comments fedilink hide all child comments
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] [email protected] 9 points 2 months ago (3 children)

    a bash script to reinstall f—ing everything again

    Why would you ever want to do that?

    First of all, almost any Arch update induced problem can be solved by downgrading the offending package to the previous version, which handily is available in /var/cache/pacman/pkg/. This is an essential Arch troubleshooting skill.

    Even an unbootable system (which has only happened once in my 10 years of using Arch because I didn't read important news) can be fixed this way, because you can always boot from the installation usb stick and then use arch-chroot to access your installation and fix problems.

    Secondly, if the problem was indeed caused by an Arch update, you will just reinstall the problem if you run a reinstall script.

    [–] sazey 4 points 2 months ago

    Honestly I only ever learnt Linux admin by troubleshooting my borked Arch updates, necessity being the mother of invention and all.

    [–] [email protected] 1 points 2 months ago* (last edited 2 months ago)

    This is an essential Arch troubleshooting skill.

    Well you see, I didn't know that haha, I know there are better ways to deal with a "defective" arch update but to me, that was the easiest, laziest way to do it and it worked most of the time. I have to admit this was a "me" problem I'm not blaming arch it's just that I grew tired of things breaking because I didn't read the news before doing pacman -Syu.

    [–] [email protected] 1 points 2 months ago

    Ah my last reinstall was because of important news I didn't read.