Linux: concerns over systemd adoption and Debian's decision to switch

Wed Oct 22 00:20:12 UTC 2014

On Tue, Oct 21, 2014 at 8:40 AM,  <Valdis.Kletnieks at vt.edu> wrote:
[snip]
> It started as a replacement init system.  I suspected it had jumped
> the shark when it sprouted an entirely new DHCP and NTP service.  And this

Yikes.   What's next?   Built-in DNS server + LDAP/Hesiod + Kerberos +
SMB/Active Directory  client and server + Solitaire + Network
Neighborhood functionality built into the program ?

I would like to note, that I prefer  Upstart as in RHEL 6.

The all-in-one approach of systemd might have a place on some
specialized desktop distros,  but outside that niche its' IMO a
terrible idea.

The proper fix is probably a go back to Upstart or SysVInit  and
rewrite systemd,  so all the pieces are separated  and exist as a
higher layer on top of init.

Nothing wrong with having a   concept such as a
"systemd-desktop-program-launcher"   application that the real  init
system runs.

> was confirmed when I saw this:
>
> "Leading up to this has been cursor rendering support, keyboard mapping
> support, screen renderer, DRM back-end, input interface, and dozens of other
> commits."
--
-JH