systemd cat and GNU cat hugging a Linux cat.

you are viewing a single comment's thread
view the rest of the comments
[–] 138 points 1 year ago (5 children)

Why should I not use systemd?

  • source
  • hideshow 10 child comments
  • [–] 96 points 1 year ago (3 children)

    When you want to feel special but not enough to go to the effort of using FreeBSD

  • source
  • parent
  • hideshow 6 child comments
  • [–] 40 points 1 year ago* (2 children)

    because the over 70 different binaries of systemd are "not modular" because they are designed to work together. What makes a monolith is, apparently, the name of the overarching project, not it being a single binary (which again, it's not)

  • source
  • parent
  • hideshow 4 child comments
  • [–] 8 points 1 year ago

    What makes it a monolith is that the 70 binaries refuse to do their one job (see: Unix philosophy) independently.

    A few months ago, a systemd update broke my boot process because I dared set up my device-mapper nodes manually in a minimal initrd without having a second copy of systemd in there as well. The device is there, yet systemd times out "waiting for device". How come then a manual mount -a in the rescue shell works then?

    If course, the bug had already been reported and swiftly rejected by L. "Hurr durr bother your distributor not me" Pottering.

  • source
  • parent
  • [–] 11 points 1 year ago

    If you have to ask, then there's no reason not to. It's people who tinker with their systems that encounter issues with it, or more often random annoyances that add up over tme to those memes.

  • source
  • parent