4 ms·

This is a pretty bad list of issues with systemd. A large portion of criticisms in this list seems to be due to a misunderstanding of the author about what is

This is a pretty bad list of issues with systemd. A large portion of criticisms in this list seems to be due to a misunderstanding of the author about what is actually in the systemd git repo. The git repo contains udev and other deamons in addition to the init process. As a result, most of the claims on this page about things going in to the init process are incorrect. If you look the actual release notes they are usually referencing a completely different daemon. For example the line 'pid 1 does DNS' points to a release note about a separate daemon called 'systemd-resolved'. edit: grammar

deleted 11y ago
[deleted]
digi_owl 11y ago
Well the devs has brought that on themselves by naming the init binary and the overall project the same, and then dumping more and more into a singular code repository.
- eeperson 11y ago
  So its the systemd developers' fault that this is not a very good list of issues?
  - digi_owl 11y ago
    They could have killed the confusion early by either renaming the init (or the project), or keeping the daemons in a different place from the Systemd init code. But instead they lump more and more into a single tree. You can't just grab the Resolved code to look at it, you have to grab the whole Systemd ball and then extract the portion related to Resolved. And will Resolved even function without Systemd sitting as the init?
- davidstrauss 11y ago
  The entire BSD kernel and init system are all in one repository. Are those developers "bringing on" confusion by doing that?
  - digi_owl 11y ago
    If you want to make a BSD do so, do not turn the whole of Linux into one. Gah, i keep using source repository when i should be using source tree...