Marc Chamberlin said the following on 04/10/2013 04:57 PM:
Given that the YaST Runlevel editor is broken (Bug 800514) in openSuSE12.3, and it appears that the switch-over to systemd is still a work in progress,
Indeed. Just like the kernel is a 'work in progress'; along with KDE4, Gnome, and everything else I have running under all the versions of Linux I have. Are you hinting that something like Windows is _not_ a work in progress? (I realise that too can be taken more than one way!)
my question is this - Is the only workaround, to automatically starting up services during boot up, is to go in and manually create the links in the /etc/init.d/rc*.d directories for the various services one needs?
I can't see how that would be a work-around, and you haven't make it clear what it would be a work-around for. If you want to add services for boot time, well that's what the 'systemctl' command is for (option: 'enable'). If you want to start them right away, well that's what the 'systemctl' command is for (option: 'start'). I realise that the 'systemctl' command (or its GUI equivilent) are really just wrappers around the mechanism for symbolic links; heck the man page even says that! But it saves me having to specify a path.
That is going to be a real PITA trying to figure out by hand the order in which all our services must be started and stopped. Anyone have another better workaround solution?
No; systemd make it a lot clearer the order in which things get started and stopped. Its called a dependency tree. http://forums.fedoraforum.org/archive/index.php/t-266768.html Things that aren't dependent on each other can be run in parallel. In fact systemd *IS* the "Better Workaround". Better because it overcomes so many problems that can and do arise with the sysvinit approach. All of which is well documented. q.v.
BTW - This is the second major bug I have now encountered in trying to install and use openSuSE12.3. (The first was, and appears it may still be, Bug 809843 which was a showstopper for me.) Can't say I am very impressed with this release, and am thinking about dropping back to 12.2 (or perhaps even earlier) for our servers and gateway systems and wait until 13.x comes out....
You problem isn't with 12.3. I had systemd working well in 12.2 The reason I had it working was that I let go of the sysvinit approach - abandoned it altogether. Having admitted that to myself I had no real problem, no show-stoppers, just more reading of the man pages etc and improving my understanding of systemd. If old, decrepit, superannuated alzheimer-candidates like Patric and myself can manage that, I'm sure that younger, more nimble minds can manage it as well. -- Who are you to question why your God doesn't want me to believe in him? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org