Hello,
init 1 is not working anymore ?
It’s switching back to login and runlevel repots the default runlevel 3
Is there a other command?
Best regards
I am not in a position to test this but I wonder if you might try this terminal command:
sudo /bin/systemctl isolate rescue.target
Let us know if this works for you.
Thank You,
On 07/18/2012 10:26 PM, achimk wrote:
> Is there a other command?
i have not used either 12.1 or 12.2 yet but i think init 3, init 1 and
etc etc are all tied to the systemV which was replaced with systemD in 12.1
are you familiar with the differences between the two? if not you
probably need to do some reading on it…(reading that i have not
done–so far i’m real happy with 11.4 and systemV)
–
dd
systemd implemented the old init N commands for convenience. They get translated to this kind of command, that you can see in the comment of jdmcdaniel3 (systemctl isolate …)
I’m also happy with my openSUSE 11.4 and systemv.
But for some reasons (professional) i need to know this.
I found a good explanation here:
Systemd - FedoraProject
systemctl isolate runlevel1.target
systemctl isolate runlevel2.target
systemctl isolate runlevel3.target
But it isn’t working correct on openSUSE 12.2 RC1
If i use
systemctl isolate runlevel1.target
the console is not usable anymore.
The others are usable!?
Only the network is stopped.
No single user target ? It seems so.
systemctl list-units --type=target --all
i see all targets for this runlevel, but i don’t know if i’m
in runlevel3 or runlevel1, this is bad.
The Fedora site reports that /etc/inittab is not used,
in openSUSE it is used.
I used yast/runlevel-editor and changed the runlevel and watched the inittab-file,
it changed.
And i saw the a runlevel 1 can not set up.
This is all strange and weird…
Best regards
On 07/18/2012 10:26 PM, achimk wrote:
> init 1 is not working anymore ?
i just saw this on the mail list:
Le jeudi 19 juillet 2012 à 12:49 -0400, Roman Bysh a écrit :
> Hello List mates,
>
> Has anyone been successful starting “init 1” in RC1?
>
> systemctl isolate runlevel1.target
>
> Try it and see what happens.
Open a bug report in bugzilla please.
– Frederic Crozat <*******@suse.com>
SUSE
so, you should be able to go to bugzilla, find the newly created bug and
follow along…maybe even contribute to it, and that is what testing a
new release is all about–finding and fixing bugs…
–
dd http://tinyurl.com/DD-Caveat http://tinyurl.com/DD-Hardware
http://tinyurl.com/DD-Software
What does DistroWatch write about YOU?: http://tinyurl.com/SUSEonDW
systemctl isolate rescue.target
Nothing changed, network is still active (ifconfig)
But
systemctl list-units --type=target --all --no-pager
shows that he network.target is inactive/dead, but
ifconfig shows the devices and the ip-addresses.
(and “init 1” , “ps ax” and “runlevel” are easier to use).
Also strange and weird…
It would be nice to have runlevel1-like state back,
who needs runlevel2, i do not. Cause network seems still active.
It seems that sysvinit only is not possible anymore.
Best regards.
I have created a Bugzilla report due to the fact the user has no prompt that they are in “runlevel 1” or “rescue mode” under systemd.
https://bugzilla.novell.com/show_bug.cgi?GoAheadAndLogIn=1&id=772312I encourage you to review it. If you are going through something a little different please create a new bug report.
It’s very easy to create.