5 ms·
That is pretty much the issue: to some, systemd is too many things. Realistically, one tends to take or leave an upstream package since picking and choosing pi
by blihp 7y ago
That is pretty much the issue: to some, systemd is too many things.
Realistically, one tends to take or leave an upstream package since picking and choosing pieces of it is far more work than a typical package maintainer takes on. Also, upstream design decision changes can make doing so problematic down the road.
- bonzini 7y ago> picking and choosing pieces of it is far more work than a typical package maintainer takes on. Not necessarily. RHEL does not ship gummiboot, timesyncd or networkd for example; it uses grub, chrony, NetworkManager. On my raspberry pis running Debian I have systemd as pid 1, one runs ConnMan (it connects to wireless) and the other runs networkd (it connects to Ethernet).
- aerique 7y agoThe article mentions that Debian does not have these "embrace, extend" problems yet because they've been using a fairly old version of SystemD, but they are going to run into those issues when they upgrade.
- bkor 7y agoThe distribution I use uses a much newer version of systemd. There still isn't any issue not using things mentioned like e.g. networkd and so on.