70
Why do you use a systemd-less distro (if you do)? (programming.dev)
submitted 2 days ago by to c/linux@programming.dev
65 comments fedilink hide all child comments
 

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

you are viewing a single comment's thread
view the rest of the comments
[–] 2 points 1 day ago* (last edited 19 hours ago) (8 children)

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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 8 child comments
    •
  • [–] 1 point 1 day ago (7 children)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 7 child comments
    •
  • [–] 1 point 1 day ago (6 children)

    Lol, you are a clown. First one on the list.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 0 points 23 hours ago (5 children)

    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
  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] 1 point 22 hours ago* (last edited 17 hours ago) (4 children)

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

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 1 point 21 hours ago (3 children)

    How ironic!

    Now post the output:

    ls -ld /run/systemd/io.*
  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 1 point 19 hours ago* (2 children)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 13 hours ago (1 child)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •