[mdlug] Systemd Should Be A Fork -- Why Is It Not?

[Adam Tauno Williams]

On Tue, 2015-09-01 at 10:41 -0400, A. Zimmer wrote:
> On Tue, 1 Sep 2015 10:17:46 -0400
> Steve Litt <slitt at troubleshooters.com> wrote:
> You apparently do not understand the danger.  In the future more and
> more application software will convert to total systemd dependency.
> Soon, kdbus, a project of the systemd clique, will be a part of the
> actual Linux kernel and all such dependencies will be impossible to
> ignore.  When this happens, alternative distributions will be 
> essentially useless.

You do realize the kdbus is the KDE integration into D-BUS and D-BUS is
the 'official' IPC mechanism of the LINUX kernel that SystemD uses?

Do you want to build a LINUX distribution or environment without D-BUS?
 You will simply be recreating what already has been done.

> The new perception, fostered by the disgusting apathy of the common
> Linux user, is that systemd is the new and only way.

The common LINUX user wants - for example - printer discover that
*works*.  That requires integration of a lot of components; which is a
goal of SystemD. 
A USB even happens, a module must be loaded, services like CUPS need to
be notified that something possibly relevant to them happened.  Aka -
IPC, which is D-BUS, to which SystemD is a broker. 
-- 
Adam Tauno Williams <mailto:awilliam at whitemice.org> GPG D95ED383
Systems Administrator, Python Developer, LPI / NCLA