I’m curious to know why people use systemd-less distributions. Which one would you recommend to someone who wants to stop using systemd?

  • esc@piefed.socialEnglish
    0·
    1 day ago

    It wasn’t because it’s true. They are literally separate utilities. Many is exactly two (i think) busybox and whatever the other one is called. For vast majority of people and in context it should be obvious that coreutils I was referring to is GNU coreutils, you are being intentionally obtuse. There are three, I believe, mandatory parts that fall under systemd umbrella everything else is either optional or separate. Interdependency angle is disengenious at best, programs can and have dependencies, it’s laughable that you think that they aren’t separate utilities because they depend on other utility.

    Forced hegemony I’m dying lol.

    • BB_C@programming.dev
      0·
      2 days ago

      Let’s play a game. Pick a “separate utility” from the list above, and let’s see if you know what you’re talking about, or just waffling.

        • BB_C@programming.dev
          0·
          1 day ago

          First one on the list.

          % readelf -d /usr/bin/bootctl | rg -r '$1' '.*NEEDED.*\[(.*)\]'
libsystemd-shared-262-1.so
libgcc_s.so.1
libc.so.6
          • esc@piefed.socialEnglish
            0·
            1 day ago

            Are you familiar with the concept of shared libraries? Please, stop embarrasing yourself.

              • esc@piefed.socialEnglish
                0·
                1 day ago

                How boring.

                Will you ever get to the point where you say clearly why exactly bootctl isn’t a separate utility? No, having dependencies doesn’t make something not a separate utility. And no, communicating with systemd daemon over unix sockets doesn’t as well.

                • BB_C@programming.dev
                  1·
                  23 hours ago

                  Good.

                  So the tool YOU chose is NOT:

                  • standalone at the project level ✅
                  • standalone at the repo level ✅
                  • standalone at the source level (trivially shown with the libsystemd-shared.so dep without requiring looking further) ✅
                  • standalone/fully independent at the runtime level ✅

                  This and the sibling sub-thread where I mentioned presets show with actual facts how the systemd forced hegemony actually works, where it’s not just a simple case of “they just have some stand-alone cli tools under their umbrella bro”.

                  The project itself wouldn’t try to (clumsily) dispute this either, since it’s at the core of what they consider a selling point; interface unification and deeper integration with the system.

                  • esc@piefed.socialEnglish
                    1·
                    18 hours ago

                    So, you’ve demonstarted nothing and all your points were refuted. Then you’ve made up a list with checkmarks and proudly proclamed yourself right? 😮‍💨