Re:Systemd Absorbs “su” Command Functionality
by simoncion on Saturday August 29, 2015 @09:54PM
(#10142007)
> What I don't understand is how the vast majority of the Linux community is not just allowing, but encouraging, systemd to continue to grow without bound.
The vast majority of the Linux community has no influence on the development of systemd and its cloud of closely related software. What's more, Poettering & co. are notoriously opinionated and bullheaded. This makes attempts to steer "their" projects in new directions all but impossible.
If Debian had moved from SysV init to -say- OpenRC, systemd would be a strictly RedHat curiosity. [0] If my experience with Kubuntu 15.04 is typical [1], we might see some pushback from -at a minimum- Canonical.
The Linux kernel hackers asked some serious technical questions about kdbus (another Poettering Cabal project) back during the 4.1 merge window. The answers that they got back were less than satisfying. I haven't been following the kdbus project closely since then, but AIUI, the objections raised have yet to be addressed.
[0] It's a pity that that conversation was not on my radar when it first started; I would have loved to get up to speed on OpenRC and attempt to address the Debian folks' concerns with it!
[1] Systemd boot times are 2->10x slower than boot times with Upstart (and the systemd boot time reporting software provides incorrect numbers), and systemd system shutdowns occasionally hang forever, requiring the use of SysRq key combos to kill the machine.
The vast majority of the Linux community has no influence on the development of systemd and its cloud of closely related software. What's more, Poettering & co. are notoriously opinionated and bullheaded. This makes attempts to steer "their" projects in new directions all but impossible.
If Debian had moved from SysV init to -say- OpenRC, systemd would be a strictly RedHat curiosity. [0] If my experience with Kubuntu 15.04 is typical [1], we might see some pushback from -at a minimum- Canonical.
The Linux kernel hackers asked some serious technical questions about kdbus (another Poettering Cabal project) back during the 4.1 merge window. The answers that they got back were less than satisfying. I haven't been following the kdbus project closely since then, but AIUI, the objections raised have yet to be addressed.
[0] It's a pity that that conversation was not on my radar when it first started; I would have loved to get up to speed on OpenRC and attempt to address the Debian folks' concerns with it!
[1] Systemd boot times are 2->10x slower than boot times with Upstart (and the systemd boot time reporting software provides incorrect numbers), and systemd system shutdowns occasionally hang forever, requiring the use of SysRq key combos to kill the machine.