On 07/26/2016 09:58 PM, dev wrote:
On 07/26/2016 04:26 AM, Rick Moen wrote:
libsystemd0's status as a bundle of interface code that does nothing in
the absence of systemd is not because it's a library -- obviously -- but
rather because all it _contains_ is interface code that does nothing in
the absence of systemd
Well now, if that were true, it would not need to be there at all and
the apache common lib could be installed without needing that systemd
dependency. Correct?
It seems I cannot have a functioning Apache system on Debian 8 without
installing at least some minimal facet of systemd and that's problematic
if not for any other reason than simply being an unnecesary dependency.
What this all really illustrates is the insidious nature of systemd
assimilation and how far things have gone, and how far they will
continue to go.
Systemd isn't going to stop at just init. There are far to many
opportunities to embrace, extend and extinguish entire distributions.
You are not kidding me? Is that because of mod_systemd?
_______________________________________________
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
