Linda Walsh said the following on 04/13/2013 12:50 AM:
But this is precious: "even though it does make clear what is happening" -- CLEAR to WHO??? you are in Single User. Your system isn't booted. Who is it clear to?
It isn't more clear to me, since I don't know what systemd.unit = multi-user-target defines as its state. I have an idea what runlevel 3 is by looking in my rc3.d rundir. So where do I list the same scripts from systemd?
Its quite clear that you "Don't Get It". Because you talk of scripts. You won't let go of the concepts associated with sysvinit and so berate systemd for not being like sysvinit. THERE ARE NOT SCRIPTS WITH SYSTEMD Systemd does not need the shell therefore it doesn't use scripts. So its pointless to ask about lists. And it is pointless to criticise systemd in terms of sysvinit. I'd venture that "3" wasn't a state, which is why it was called a run-level, but that's being picky... The systemd tools such as systemctl will tell you more about the state - what has run and what has failed. And why. It will also tell you what has run to completion - something you can't see with sysvinit since there are no tools other than, hopefully, the system log, if the programmer was sensible enough to use logging. And as I've pointed out, with systemd you can view the dependency tree associated with a target. Dependency is an important concept with systemd and one completely absent sysvinit. -- Everything that is really great and inspiring is created by the individual who can labor in freedom. -- Albert Einstein, in H. Eves Return to Mathematical Circles, Boston: Prindle, Weber and Schmidt, 1988. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org