On 14/10/14 13:54, Miles Fidelman wrote:
Andrei POPESCU wrote:
Have you actually looked into what depends on systemd?
Trying to.
As a start - anything that depends on udev and logging come to mind;
Strictly speaking, yes, udev is part of the systemd suite. However, it
is perfectly capable of being installed and run on a Debian jessie
system without the rest of the systemd suite being installed; if it
fails to work correctly in such a configuration, that is a bug and
should be reported.
As for logging, it turns out to be the case that Debian jessie only uses
systemd-journald as part of its logging system if you are using systemd
as PID 1. On otherwise-default Debian jessie systems where systemd is
not PID 1, logging is handled directly by rsyslog, which is not in any
way shape or form conceivably describable as being part of systemd.
all
services that require startup (hmm... I run a server, not a desktop - so
that would be pretty much everything).
Per the technical committee's formally stated expectation that
maintainers will continue to support the multiple available init systems
in Debian [1], it is clearly a reportable bug for (approximately) any
package in Debian to not support init systems other than systemd.
It would also be somewhat astonishing for most services, *particularly*
those which would primarily be found in a server environment rather than
on a desktop system, to depend on interfaces of systemd-logind, which is
the main source of dependencies on a systemd suite component other than
udev/libudev.
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746715#278
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/543d2488.3050...@zen.co.uk
