• Shareni@programming.dev
    link
    fedilink
    arrow-up
    2
    ·
    7 months ago

    Also have a copy of pacman-static somewhere so that you can fix your shit in case of a partial upgrade (and trust me, it can go horribly wrong)

    Oh I know, I quickly learned to never update it without having live media nearby to arch-chroot with.

    if you make your arch system unable to boot… Don’t use arch

    The only thing I did to make it unbootable is to update it. Going by that logic nobody should use it.

    This is not my attempt at elitism. Arch was never meant to be a hassle free distro and it sure as shit is not one.

    I definitely agree, that’s why I’m commenting against dumbasses suggesting it to beginners. Especially when they glorify AUR.

    Can I offer you a Debian in these trying times?

    No need, I already landed on MX + nix after 2+ years of arch. Nix unstable gives me all of the benefits of arch (except for the DE) and then plenty more on top. Different downsides, but far less stressful. I’m

    • AMDIsOurLord
      link
      fedilink
      arrow-up
      2
      ·
      7 months ago

      You need to keep the update log and go through the whole thing and see if something needs reconfiguring. Sounds shitty? Yeah, that’s why I stopped using Arch and Gentoo despite being a veteran

      Nowadays I just install Debian or some derivative and call it a damn day. Unless you need some exotic setup (and those are more suited to Gentoo or Slackware anyway)

      • Shareni@programming.dev
        link
        fedilink
        arrow-up
        1
        ·
        7 months ago

        Oh I had a far simpler method: update and it fails to boot? Rollback and try updating again in a week. It usually works then, but I had to wait a bit more a couple of times.

        The only exception was that bad GRUB release. I think that’s the only update fail that absolutely required arch-chroot.