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

linuxmemes

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

    As a former arch linux guy, the solution to this is to be prepared by having a separate partition for home, and a bash script to reinstall f---ing everything again with a single command.

    [–] SpaceCadet@feddit.nl 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@lemmy.world 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.

    [–] jpablo68@infosec.pub 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.

    [–] PolarisFx@lemmy.dbzer0.com 1 points 2 months ago

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

    [–] Moreless@lemmy.world 8 points 2 months ago (1 children)

    You reinvented NixOS

    [–] jpablo68@infosec.pub 1 points 2 months ago

    I want to install NixOS on a laptop that I have lying around BTW.