• cheddar@programming.dev
      152·
      2 months ago

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

  • Saledovil@sh.itjust.works
    12·
    2 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
      2·
      2 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.

  • Psythik@lemmy.world
    2·
    2 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.

  • jpablo68@infosec.pub
    1·
    2 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
      1·
      2 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.

      • jpablo68@infosec.pub
        1·
        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.

      • sazey@lemmy.world
        1·
        2 months ago

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