The Debian init system general resolution returns

Posted Oct 22, 2014 15:58 UTC (Wed) by JGR (subscriber, #93631)
In reply to: The Debian init system general resolution returns by mgb
Parent article: The Debian init system general resolution returns

> Other critical packages are modular and are not trying to take over login, networking, time service, logging, package management, udev, dbus, and whatever the systemd borg decide to assimilate tomorrow.
systemd is a collection of components with well defined interfaces, it seems a bit odd to lambast it for not being modular.
If you don't want to use networkd or whatever then don't, conversely if you want to make or fork your own implementation of a particular interface then you can do that.

The Debian init system general resolution returns

Posted Oct 22, 2014 16:34 UTC (Wed) by mgb (guest, #3226) [Link] (1 responses)

Many of the systemd blob's interfaces are volatile and/or undocumented and thus inhibit future incremental improvement of Linux.

What limited interface stability promises exist are explicitly stated to be revokable:

"Note that this is a promise, not an eternal guarantee. These are our intentions, but if in the future there are very good reasons to change or get rid of an interface we have listed above as stable, then we might take the liberty to do so, despite this promise."

Systemd functions also have extremely limited reimplementability and support for non-systemd distros.

The Debian init system general resolution returns

Posted Oct 22, 2014 17:28 UTC (Wed) by pizza (subscriber, #46) [Link]

> Many of the systemd blob's interfaces are volatile and/or undocumented and thus inhibit future incremental improvement of Linux.

Citation needed.

> Systemd functions also have extremely limited reimplementability and support for non-systemd distros.

You seem to be asserting that systemd only supports distros that use systemd.