On Mon, May 12, 2014 at 11:21:15AM -0700, Josh Triplett wrote: > > I don't think I understand what you mean. What does "having systemd > > installed" mean, if not that it's being used as the init system? And if > > it isn't used as the init system (presumably because the user chose no > > to do that), why is it a good idea to change that?
> > In other words: what isn't handled properly? What should happen, and > > what does happen? > Consider a system which has systemd installed, systemd-sysv *not* > installed, and systemd used as PID 1 via init=/bin/systemd. Since > systemd-sysv is not already installed, "systemd-shim | systemd-sysv" will > pull in systemd-shim instead, which will atttempt to supply services that > conflict with systemd's. systemd-shim is bus-activated-only. The dbus name will already be claimed by systemd itself on startup, so systemd-shim will be a no-op on such a system. Stop spreading FUD. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ slanga...@ubuntu.com vor...@debian.org
signature.asc
Description: Digital signature
