all 9 comments

sorted by: hot top controversial new old
[–] 34 points 7 months ago (3 children)

Tl;Dr they all failed because they're init daemons and not entire system management daemons. Article gave a nice description of the different choices but I gave up reading after runit because the reason for failure always boiled down to

It's only an init daemon

  • source
  • hideshow 3 child comments
  • [–] 14 points 7 months ago

    More than that: "its only an init daemon that does not even make use of Linux features". They all try to work on all posix systems while systemd is Linux-only and uses everything the kernel can offer to make things safer and more reliable.

  • source
  • parent
  • [–] 12 points 7 months ago* (last edited 7 months ago) (1 child)

    Surprised to see that Dinit wasn't even mentioned.

  • source
  • hideshow 1 child comment
  • [–] 17 points 7 months ago (1 child)

    I'm pissed that systemd has made a change that paves the way for age verification, and is unwilling to go back on it. The change they added may not do much on its own, but I worry about future consequences.

    Since it's rare for large organizations and projects to go back on things like this, I'm considering moving my systems over to non-systemd distros. At the very least, I hope a fork without the userdb birthDate variable hits the AUR.

  • source
  • hideshow 1 child comment
  • [–] -1 points 7 months ago

    I don't like the law, but I don't like the phrase "It's illegal to use Linux in the state of California" more. Systemd is not a political lobbying organization, they're a software organization and its their job to make legally compliant software.

    We need to fight these laws, but being mad at Systemd isn't the solution since they aren't the culprit.

  • source
  • parent
  • [–] 4 points 7 months ago