On 2011/11/12 14:42 (GMT) Richard Brown composed:
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?
Convenience disappeared, unless systemctl is aliased to what used to work (& easy to remember, easy to convey in help forums) somehow: #runlevel S 5 init 3 <- 6 characters vs. systemctl stop xdm.service <- 26 characters, 333% more init 5 <- 6 characters vs. systemctl start xdm.service <- 27 characters, 350% more #runlevel S 5 init 2 <- 6 characters (kill: XDM, NFS, Samba, Apache, etc) vs. systemctl ???...??? (Lord only knows how many more characters to do all the above) Until easy to find, easy to understand systemd docs are universally available like those for init, I'm not going to begin learning how to switch from easy to complicated, sticking with sysvinit until then. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org