Dealing with the conflicting dbus policies?
Martin Pitt
mpitt at debian.org
Tue Oct 14 08:14:04 BST 2014
Hello Josh,
Josh Triplett [2014-10-14 7:03 +0200]:
> Given the increasing desire to install systemd-shim even on systems
> moving to systemd, both to make init=/lib/sysvinit/init work and to
> smooth the transition as part of 746578, I think we need a better
> solution for this problem than just updating systemd-shim every time
> systemd's dbus policy changes.
Agreed.
> Simple solution: given that systemd-shim exists to help run systemd
> services without systemd as PID 1, how about making systemd-shim depend
> on systemd, which contains those services?
IMHO this would be the way to go now. I think systemd-shim shipping
its own version of the policy is a leftover from the time when Ubuntu
split systemd-services, and did not install the systemd package. But
now there's only the systemd package in both Debian and Ubuntu. So I
think dropping the D-BUS policy from -shim entirely is now possible,
correct, and desirable. Steve, do you agree?
Thanks,
Martin
--
Martin Pitt | http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
More information about the Pkg-systemd-maintainers
mailing list