• Kalcifer
    link
    fedilink
    928 months ago

    There’s never a wrong time to update Arch Linux!

  • @[email protected]
    link
    fedilink
    328 months ago

    Never seen the third LotR film; I was literally about to finally watch it today so thanks for spoiling the movie for me.

  • @[email protected]
    link
    fedilink
    48 months ago

    After breaking on my notebook for the umpteenth time, i try now void. Have to fix some of my automation scripts tho.

  • @[email protected]
    link
    fedilink
    28 months ago

    Can’t complain about Arch myself, but I prefer my software to not change. I’m back on Mint 22 with Plasma 5 and Wayland and I absolutely love it.

  • @[email protected]
    link
    fedilink
    58 months ago

    I used arch over 5 years in the past. Isn’t it common today checking the update news on the arch wiki before updating?

    • @[email protected]
      link
      fedilink
      38 months ago

      It’s not the kernel but always mkinit in my case, on multiple machines. Even if i did never do nothing related. And booster/dracut and Efistub somehow never worked.

    • @[email protected]
      link
      fedilink
      38 months ago

      Been using EOS a lot longer and always flawless.

      The only problem I have had is leaving a system too long and having to remember how to get the damn keyring to refresh. That is my biggest complaint.

  • @[email protected]
    link
    fedilink
    108 months ago

    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.

    • DefederateLemmyMl
      link
      fedilink
      108 months ago

      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.

      • @[email protected]
        link
        fedilink
        1
        edit-2
        8 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]
        link
        fedilink
        48 months ago

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

  • Lucy :3
    link
    fedilink
    348 months ago

    Never had problems with that tbh, only with NVidia. Even on testing.

  • @[email protected]
    link
    fedilink
    78 months ago

    I don’t have time for my system to be getting borked once a week. That’s why I use Debian. My system getting borked once every 2 years isn’t that bad.

    • @[email protected]
      link
      fedilink
      138 months ago

      The moment I finally installed Arch was then I felt “freedom” for the first time. No longer do I need to make compromises on my system and have things installed that I don’t need or want. It’s my system that I put together the way I like it. A bonus is that I know my system pretty well if something should break and I have the wiki to guide me