![](https://seccdn.libravatar.org/avatar/d8c5bb1289039c7e6dfcc509923d4ac6.jpg?s=120&d=mm&r=g)
On Thursday, April 11, 2013 11:33:45 AM Anton Aylward wrote:
Damon Register said the following on 04/11/2013 10:24 AM:
I didn't really notice anything different in the YaST runlevel setting. Do I understand correctly there is a significant departure or shift in use of runlevel or how it works? Is there anyone who can help me understand this discussion?
It depends on whether your system is running with systemd or sysvinit. You can use zypper (or rpm) to what/which is installed.
Systemd has a backward compatibility function so commands such as init 3 and init 5 still appear work. Many things that still appear to exist under /etc/init.d are actually 'aliased' to their systemd equivalents.
Even though the init commands still work I have been using [CODE] systemctl isolate runlevel3.target and systemctl isolate runlevel5.target [/CODE] A few more key strokes but they do work. A lot more I need to learn about this new stuff, especially how to tell a service to start at boot or level 3, 4 or 5, etc.
For the ordinary user, so long as there are no hardware problems, it should be the same old "turn it on, wait a bit and see the login screen".
Unless you're specifically interested, in which case there is a vast amount of documentation, there's little reason to look "under the hood".
-- HTTP is like being married: you have to be able to handle whatever you're given, while being very careful what you send back. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Russ -- openSUSE 12.3(Linux 3.7.10-1.1-desktop x86_64)|KDE 4.10.2 "release 553"|Intel core2duo 2.5 MHZ,|8GB DDR3|GeForce 8400GS(NVIDIA-Linux-x86_64-310.32) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org