• cheddar@programming.dev
      link
      fedilink
      arrow-up
      24
      arrow-down
      2
      ·
      10 months ago

      A wrecked bootloader is not a problem, but a lesson to keep a usb drive to be able to chroot.

  • Psythik@lemmy.world
    link
    fedilink
    arrow-up
    31
    arrow-down
    1
    ·
    10 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.

    • DaTingGoBrrr@lemmy.ml
      link
      fedilink
      arrow-up
      10
      ·
      10 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

  • Saledovil@sh.itjust.works
    link
    fedilink
    arrow-up
    15
    arrow-down
    1
    ·
    10 months ago

    I tried arch once. Eventually, my computer just showed a black screen on booting. I managed to fix it by resetting my bios. That was the end of that attempt at using arch. Still want to try again, though.

    • Lulzagna@lemmy.world
      link
      fedilink
      arrow-up
      8
      ·
      10 months ago

      I had this happen once or twice, caused by bad Nvidia drivers with Wayland.

      I use AMD now for my day job, haven’t had a single issue in over two years. That’s not to say you should use it - it’s still a rolling release distro and will always have a potential to break over most other distros.

    • zarkanian@sh.itjust.works
      link
      fedilink
      arrow-up
      4
      ·
      10 months ago

      And I like having my software up-to-date. It sucked ass when I was on Mint and one of my favorite programs had an update and I had to wait months for it to hit the repos.

    • icedterminal@lemmy.world
      link
      fedilink
      English
      arrow-up
      3
      arrow-down
      1
      ·
      10 months ago

      It’s always been bad practice to just blindly update software. That’s why we have different distros.

      Ubuntu and Mint hold your hand and make it easy for newcomers. Great way to dive into Linux. I completely agree these are great for “it just works” and no fuss. I’ve not had one break on me.

      Arch and Gentoo expect you to have experience and know what you’re doing. You build it up how you want it. That’s what makes these so great. But you need the experience and knowledge.

      I’ve personally tried openSUSE and in my opinion it feels like a good middle ground between both ends. In the past I’ve recommended Mint to get started, openSUSE once you’ve got experience, and then Arch for when you want total control.

      • Possibly linux@lemmy.zip
        link
        fedilink
        English
        arrow-up
        2
        ·
        edit-2
        10 months ago

        I’ve never really had an issue in the 7 years I’ve used Linux. I don’t use Arch BTW.

        My server OSes all run Debian which can auto update reliability with automatic reboots that happen staggered overnight.

  • jpablo68@infosec.pub
    link
    fedilink
    arrow-up
    8
    ·
    10 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@feddit.nl
      link
      fedilink
      arrow-up
      9
      ·
      10 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.

      • sazey@lemmy.world
        link
        fedilink
        arrow-up
        3
        ·
        10 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
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        10 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.

  • FiskFisk33@startrek.website
    link
    fedilink
    arrow-up
    6
    ·
    10 months ago

    I am totally ready for it, I know it’s a thing, especially since I drink the forbidden nectar that is the AUR. Yet I’ve never had this happen even once.

  • Samsy@lemmy.ml
    link
    fedilink
    arrow-up
    5
    ·
    10 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?

    • MonkderVierte@lemmy.ml
      link
      fedilink
      arrow-up
      3
      ·
      10 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.