• Auli@lemmy.caEnglish
    1·
    1 day ago

    For servers ways. For laptop today after last air attack. I know air “isn’t” arch. But without it arch has a lot less packages.

  • mazzilius_marsti@lemmy.world
    7·
    2 days ago

    ex arch user for 5 yrs

    current fedora user since 2024

    i’ve been getting a lot of “recommended” youtube videos on gentoo and nixos

    send help plezz

  • No Thanks@lemmy.4d2.org
    3·
    2 days ago

    The first time debian oldstable broke a package after an incremental update, i reconsidered my long running hard stance against arch

    Updated my endeavour install last night from 6.18 to 7.1 without issue: daily -Syu is for the birds

    • fartsparkles@lemmy.world
      451·
      3 days ago

      100%. I’ve got servers running arch for the past 5 years or so and they’re the most stable systems I’ve got. I got so tired of the painful upgrade paths on “stable” distros so decided to switch a server to a rolling release.

      After I found arch got security patches into the repos faster than the stable distros could backport, I decided to switch them all over.

      I’m even a mad man and have them self update with a script that checks informant (or something, can’t actually remember) for installed packages against news. If no installed packages are found in news, it continues with the scheduled update.

      It’s glorious.

        • metallic_z3r0@infosec.pub
          3·
          2 days ago

          Especially when customizing the kernel is the default experience with Gentoo, reducing the theoretical attack surface even more if you know what you’re doing.

      • Lucy :3@feddit.org
        1·
        3 days ago

        If you want to have at least some thrill, use testing repos. I had to fix GitLab two (2) times due to the main package not being linked against testing libraries (it took 10 seconds to ln -s the new to the old version), and had one breakage due to dovecot revamping their whole config system, but publishing no example/useful docs.

      • Ooops@feddit.org
        1·
        3 days ago

        I was too lazy for scripting the update to check the news and just get a mail when the update has issues… or should get one.

        In reality I check if the email process still works once every blue moon because I didn’t get one from a failed update in years.

  • GaumBeist@lemmy.ml
    11·
    2 days ago

    What about you? When did you choose stability over the rolling release?

    This is such sloppy engagement baiting. If it was just a hot take shitting all over one of the larger linux communities, that would be one thing, but to follow it up with a “let me know in the comments” just makes it all feel disingenuous and like somebody is being sponsored by NordVPN or Incogni to post their ragebait

  • NominatedNemesis@reddthat.com
    2·
    2 days ago

    Arch user (btw) here. I use xorg and a custom tiling window manager. I had 0 breakage regarding my config. Nvidie fked me 2 times and grub was broken 1 time. Thats it. 10 years 3 chroot. Pacman runs when I feel like it. I used two weeks to configure my setup, and I hardly ever change a thing nowdays.

    Tried Hyperland on an “old” thinkpad, each update broke something. So no thanks, I’ll stick to mature, battle tested components, where my config and sanity will remain stable, and leave the tamagotchi for ricers/thinkerers.

  • Digit@lemmy.wtfEnglish
    3·
    2 days ago

    Stable over rolling release?

    These are not mutually exclusive.

    Can haz stable rolling.

    E.g. use Gentoo, and avoid the ~ and ** keywords.

    Gentoo’s all about choice. You can choose to configure it so it does not require hand holding, and running it like a tamagochi. Or you can choose to fiddle with it so much it’s very time demanding… not the compiling, so much as the system configuration management. There’s official binhost now anyway. But then, if you’re fiddling around alot, you’ll send emerge to compile rather than just get a binary, to meet all your exacting nuances of configuration.

    I have one gentoo that’s been rock solid for … about 17 years, with only one blip of downtime when there was a fire. No hand-holding.

    Arch is indeed a different beast. In my experience, it’s only a matter of (relatively short) time before Arch eats its kernel or some other catastrophe that requires rescue or abandon.

    Respect to Manjaro for what they try do, offer arch with more stability (and conveniences).

    On a whim, just now, I made this

    Arch Faceplant image of archlogo skateboarder faceplanting with sudo pacman -Syu skatebloard in air

    But, then, I hear many things have changed in arch, since I last used arch (just before the switch to systemd)… and maybe things have changed, and it does not do that any more…?

    `

    And then also, can haz arch/artix/etc in a bedrock stratum… then it can carry on in its bloody rolling risky churn, in a safe space, where the more stable strata can pick up the slack when arch tries to faceplant itself again.

  • sunglocto@lemmy.dbzer0.com
    101·
    3 days ago

    I’ve made ~6 Arch systems at this point. None of them have randomly broken on me, none of them have broken after an update and to be honest have been solid. I have no idea where the narrative of Arch being able to destroy itself at any point came from, but I don’t think it’s true at all.

    • dragonlover@lemmy.zip
      2·
      2 days ago

      Its because people grab it randomly and then blindly install off the AUR

      I was nervous to switch to arch at first because of all the jokes, but it’s honestly been pretty slick. My servers are all on Debian but I put arch on my daily driver and the most “tomogachi tinkering” I’ve done has been Bluetooth nonsense, which is a general problem on most distros.

  • sanpo@sopuli.xyz
    601·
    3 days ago

    Ironically, it’s the rolling release that’s much more stable for me.

    “Stable” distros often had a long and risky process of upgrading to the next major release.

    Meanwhile, my Arch install has been pretty damn stable for over 10 years and went through several different PCs.

    • ranzispa@mander.xyz
      6·
      3 days ago

      Fair, I’m always scared to upgrade to a new Debian release and the process is always painful. But that happens every couple years and I can take a week or two to look into it before doing it.

      Every time I did pacman -Syu it was a Russian roulette. Most of the times everything was fine, but often enough there was a problem and something was broken and I had to spend a couple days figuring out what was the problem.

      • Ooops@feddit.org
        3·
        3 days ago

        I’m always scared to upgrade to a new Debian release and the process is always painful.

        At least in my personal experience this is one of the big triggers for distro hopping. Most of the people I know that stuck to one distro for years and years are on a rolling release.

          • Ooops@feddit.org
            1·
            2 days ago

            That’s my point. A version upgrade having issues would have forced you to do it by now.

        • ranzispa@mander.xyz
          1·
          3 days ago

          I mostly run Debian on servers. I do not want a rolling release on a server, at all. I don’t care how well they check their packages, I just want the thing to work. I do not care about new features, I just want it to work.

    • jatone@lemmy.dbzer0.comEnglish
      6·
      3 days ago

      Same, and next year when bcachefs has nailed down the kinks it’ll be basically bullet proof with snapshotting prior to its daily updates.

    • eleijeep@piefed.socialEnglish
      72·
      3 days ago

      You’re confusing two different meanings of stable. When people refer to “stable” distros such as Debian, they are referring to the meaning of stable as “unchanging,” not the meaning of stable as “doesn’t crash.”

      A rolling release distro by that definition cannot be stable.

  • Laurel Raven@lemmy.zipEnglish
    3·
    2 days ago

    Went the other way, moved from Mint 22.3 to OpenSuSE Tumbleweed. Rolling release with solid testing before updates are pushed, any breakage during testing and they don’t push that day’s update, and if something does slip through and break things, just boot into the pre-update snapshot and wait a day to try again with the next patches.

    Up to date packages with low hassle, so as long as I don’t need stable-as-in-never-changes, it’s great.

    Also, nice to have KDE 6 finally and to have KDE not be a forgotten afterthought (Cinnamon is nice but I always feel like I’m limited compared to KDE)