Okay, maybe I'm missing something in this long debate..but, what exactly is the problem here? systemctl doesn't have the same concept of runlevels as sysvinit init 3 used to be a convenient way of booting a system that had X installed without loading X systemctl disable xdm.service is arguably just as easy a way of accomplishing the same thing with systemd, with systemctl start xdm.service being how you'd start X when you want it, systemctl stop xdm.service being how to stop it when you're done with it.. Am I missing something here?
Rüdiger Meier 11/12/11 2:32 PM >>> Sry for messing up the thread, my MUA was fighting against me.
On Saturday 12 November 2011, Carlos E. R. wrote:
On Saturday, 2011-11-12 at 14:58 +0100, Rüdiger Meier wrote:
3. If you don't use any feature of kdm at all why you should use it then? Speaking for me I don't use any kdm feature except typing my password whitch works even better without kdm.
ConsoleKit. It needs the login manager. Once I had a bugzilla where I could not hibernate, and that was the reason.
If this is true then it's another bad example for the more and more evil dependency hell. Why on earth one should need a login manager just to hibernate the machine? cu, Rudi -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org