News for hackers. Stuff that matters.

A comment on Debian reconsiders init-system diversity. Parent comment

Re:Debian reconsiders init-system diversity by blihp on Tuesday November 12, 2019 @02:26AM (#21512196)
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.

[ Parent | on HN ]
Re:Debian reconsiders init-system diversity by bonzini on Tuesday November 12, 2019 @03:01AM (#21512360)
> 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).

[ Parent | on HN ]
Re:Debian reconsiders init-system diversity by aerique on Tuesday November 12, 2019 @07:20AM (#21513478)
The 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.
[ Parent | on HN ]
Re:Debian reconsiders init-system diversity by bkor on Tuesday November 12, 2019 @12:29PM (#21515971)
The 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.
[ Parent | on HN ]