• sonofearth@lemmy.world
    102·
    2 hours ago

    Why don’t people just use Arch directly instead of using derivatives? Well… I can understand using something like CachyOS as it has a different kernel with optimisations but Manjaro feels very irrelevant. If you just want Arch Linux with simple installation, just use the archinstall script. Regardless of which derivative you use, Arch based distros are going to be heavy maintenance than something like Bazzite, Mint or Ubuntu.

    • lemmydividebyzero@reddthat.com
      1·
      7 minutes ago

      My thinking process:

      I had Debian and was not satisfied with the fact that I had to wait ages for updates of stuff like KDE Plasma. I wanted something with shorter update intervals.

      I decided against Ubuntu because of the company behind it.

      I decided against Mint, because it’s on level 3 in the derivate tree, so more places where something can go wrong.

      Then I found Manjaro and liked it from the beginning. Very easy to install (no script necessary), awesome custom Plasma theme, short update intervals, …

      Arch can be scary. I wanted a reliable, easy OS for private use and I knew, I get that with Manjaro. With Arch, I was not sure whether I might FCK something up.

    • rhubarbe@tarte.nuage-libre.frFrançais
      2·
      40 minutes ago

      Manjaro differs from Arch in terms of update cycles. They are not rolling like Arch but adhere to some monthly-ish release cycle. Which i love by the way.

      • sonofearth@lemmy.world
        2·
        25 minutes ago

        Then why not just update vanilla Arch itself on a monthly basis? Or just use something like Fedora or Bazzite. Using Manjaro kinda defeats the whole purpose of using Arch Linux. It is like getting someone to select your custom PC parts and letting them build your PC. You technically still have a custom PC but is it really?

        • rhubarbe@tarte.nuage-libre.frFrançais
          1·
          3 minutes ago

          Those cycles are meant for testing a coherent set of versions. If you update Arch on a monthly basis I’m not quite sure you got the same testing. I’ve been running Manjaro for 8 years now (laptop for business and family stuff) and I can’t remember any issue with it. I also have Endeavour and Debian on my desktop (gaming / casual) and server.

  • SavvyWolf@pawb.socialEnglish
    141·
    4 hours ago

    It’s still technically automaton if your workflow depends on people poking you when things break.

    • LurkingLuddite@piefed.socialEnglish
      342·
      13 hours ago

      Not just with their web hosting. I’ve had so many updates break random crap it’s not even funny. Recently, a random update I did not approve suddenly had kwallet not working. A core piece of a DE they provide a bundled version for. I had to start kwalletd myself every time I wanted to use it.

      It didn’t start that way on the fresh install. I didn’t do anything myself except reboot. Then suddenly my scripts that nab from the keystore are failing and asking me for passwords and what a mess.

      That’s just a more recent example. I remember having quite a few random issues on update in the past, though the only other one I explicitly remember is the DE suddenly failing to start. Like, at all. Luckily I had a recent timeshift backup saved elsewhere, restored, and ignored the update notifications for a long while…

        • eli@lemmy.world
          3·
          5 hours ago

          I tried it out like 5 years ago. A month after using it a random update broke the DE.

          Right then and there I wrote off the whole distro and haven’t touched it since.

          I don’t know why people are even using it all these years later.

        • Eldritch@piefed.worldEnglish
          16·
          9 hours ago

          The one thing manjaro had going for it was it was easy install arch. Now we have endeavor, garuda, cachy, and several other easy install arch. Including archinstall. Who all follow vanilla arch much closer, not introducing major breaking changes. There’s literally no good reason to still use manjaro.

          That said the servo aur is currently broken under catchy. Unable to update for the last couple of weeks. But that’s been my only hiccup. And a negligible one at that.

  • NewNewAugustEast@lemmy.zip
    101·
    15 hours ago

    Wow. How does this happen when letsencrypt exists? Or certbot?

    More importantly… How does this happen again?

      • Possibly linux@lemmy.zipEnglish
        2·
        2 hours ago

        There is a significant amount of infrastructure that does not support cert bot out there.

        Skill issue

      • zr0@lemmy.dbzer0.comEnglish
        171·
        12 hours ago

        Uhm. “A significant amount of infrastructure”? Uhhhm. Put a reverse proxy in front of your webserver? Problem solved? Or use log analyzers? With alerts?

        There is literally no excuse.

        • Kushan@lemmy.worldEnglish
          1·
          3 hours ago

          I think he’s referring to certain enterprise switches and other networking gear that has basically zero support for automation.

          For me personally, I would be replacing that equipment but some businesses would rather pay a few hundred bucks every year + manpower to replace the certs than a few thousand once to replace the equipment.

          • cole@lemdro.idEnglish
            2·
            3 hours ago

            …you don’t need your networking gear to support this in any way

      • Ŝan • 𐑖ƨɤ@piefed.zipEnglish
        22·
        14 hours ago

        There is a significant amount of infrastructure that does not support cert bot out there.

        Example? I believe you, I just can’t imagine what would preclude a public-facing server from using Caddy or certbot. Certainly not for a project maintaining an Arch-derivative distribution.

        • lankydryness@lemmy.world
          10·
          14 hours ago

          I don’t have a concrete example but I’ve talked to an online friend who works in IT and he claims the majority of his work is just renewing and applying certificates. Now he made it sound like upper management wanted them to specifically use a certain certificate provider, and I don’t know their exact setup. I of course have mentioned certbot and letsecrypt to him but yea, he’s apparently constantly managing certs. Whether that’s due to lack of motivation to automate or upper managements dumb requests idk

          • Ŝan • 𐑖ƨɤ@piefed.zipEnglish
            42·
            7 hours ago

            Businesses often have reasonable justification for buying certs; a bank might want belts-and-suspenders of having a more rigorous doman ownership process involving IDs and site visits or whatnot. It’s a space where cert providers can add value. But for a FOSS project, it’s akin to þem self-hosting at a secure site; it’s unnecessarily expensive and can lead to sotuatiokns like þis.

          • RobotToaster@mander.xyz
            17·
            13 hours ago

            LetsEncrypt only does level one (domain validated certificates), it doesn’t offer organisation or extended validation.

            Basically they only prove you control example.com, they don’t prove you are example PLC.

      • NewNewAugustEast@lemmy.zip
        16·
        14 hours ago

        I am trying to figure out how my little non interesting domains have kept certified for decades now without lapsing, while they can’t seem to keep it together even after a failure.

        Hard to imagine that they are so big that people simply forgot to get notices or manage the certs after it has happened so many times before.

      • surewhynotlem@lemmy.world
        71·
        14 hours ago

        There is a significant amount of infrastructure that does not support cert bot out there.

        Then there should be a significant amount of infrastructure behind something like caddy.

    • angel@sopuli.xyz
      45·
      13 hours ago

      At least the sixth time even. Four cases are documented here and another one was just three months ago. This last link points to reddit, but there a manjaro maintainer also explains why it keeps happening:

      Politics within the project are the issue.

      The fix for these issues have been build for about a year already. But those who have access to stuff like DNS and hosting are currently incapable of making any agreement on any topic preventing trivial fixes such as this from being implemented.