On Sat, 2012-09-08 at 18:57 -0400, Patrick Shanahan wrote:
* Felix Miata <mrmazda@earthlink.net> [09-08-12 14:57]:
Is init command no longer supposed to symlink to or call whatever immemorable 3X-15X command string is supposed to replace it?
I just booted with 3 on cmdline, logged in root, then issued 'init 1'. Instead of dropping to single, it went all in (runlevel 5, starting KDM) instead of shutting down network services and giving me a chance to restart everything single doesn't require, by subsequently issuing an init 3 command.
re: init 1 takes you to runlevel one and immediately back to runlevel 5.
I have noticed that "init 1" does not work as previous, but...
issueing "init s" will leave you in "single user mode" (previous init 1) and allow root login and subsequent operations.
but(again)... init 3 from "single user mode" does not get you to text level but gives you an X login screen (runlevel 5).
runlevels as such and reaching them via init 1-3 apparently are no longer supported but I haven't bothered to research systemd docs to see replacement commands.
Hm. I just tried re-installing systemd-init on my 12.1 laptop, and 3 on the cmdline worked more or less as before (modulo some breakage). systemd.unit=runlevelN.target appears to be the new/improved way to spell 'N', but that doesn't appear to be mandated as of 12.1 at least. /sbin/telinit is also provided by both sysvinit-init and systemd-sysvinit in 12.1. The systemd <==> runlevel connection is nicely documented as well, so I'm hopeful that it isn't an intermediate step in the systemd "weaning" process. (systemctl isolate runlevel3.target is progress? Oh dear.) -Mike -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org