I am currently using Windows on an older HP Laptop, which I intend to replace with a Framework 16 by next summer, but my Desktop PC at home has been running EndeavourOS, my first ever Linux distro, since last summer, so I have some Arch-based experience.

As a learning experience I’d like to install raw Arch, but I’m wondering if it makes sense as a primary OS on something that should be a stable system, since I intend to use the laptop for university. I am planning on using btrfs and timeshift, so it shouldn’t break too horribly, even if something goes wrong (and I don’t wanna jinx it, but so far my EndeavourOS pc has been entirely fine too, so I didn’t even run into such an issue yet), but depending on who you ask Arch is either the most stable distro they’ve ever used or bricked their pc ten seconds into the install process.

So now I’m curious on if you all think this is a stupid idea or if it should be fine. Should I try installing Arch and then for actual use replace it with another distro like Debian LTS, NixOS or something like Mint on a machine which fulfills a more critical role than my PC at home, or should I be alright rolling with Arch on my uni laptop?

As a side note, what’s your take on using Arch vs EndeavourOS? It’s roughly the same fundamentally, so is there any point in using Arch apart from the learning experience and being able to say “I use arch btw”? My reasoning for actually wanting to use it and not just wanting to set it up for the learning experience and then switching off to EOS or something entirely different is “I think it’s neat”, which is hardly a good reason long-term.

  • Kongar@lemmy.dbzer0.comEnglish
    8·
    1 year ago

    Arch isn’t inherently unstable. It’s just that most users don’t maintain it properly. Tips:

    1. learn to backup for real: rsync, borg, etc. you broke something? Just back up to that image you made right before you updated ;)
    2. use flatpaks. It’s kind of hard to run into AUR or dependency issues if you’re as close to a base arch install as possible.
    3. read the maintenance page and understand it. You can’t just “yay” every week and be done with it. You need to know how to handle pacnew, read the wiki for manual interventions, look for errors and warnings in the pacman log, etc. it’s not hard at all once you figure it out, but it takes a little learning.
    4. you don’t need to update every day. If it’s working - you can just let it ride. If you don’t update forever, then just update your keyring first and you’ll be good to go.

    Use what you like - it’s all stable enough.