On Sunday 13 November 2011 03:51:23 Carlos E. R. wrote:
On Sunday, 2011-11-13 at 03:04 +0100, Carlos E. R. wrote:
Could you - just for testing - try using kdm instead, and see if "init 3" behaves as it should then? I kind of suspect it will
Ugh. It is a very small setup inside Vmware Player. Kdm brings a lot of packages... Ok, I'll do it.
Now it is 02:56. It will take time to download.
Almost 400MB compressed. Now it is 3:49. But you were right, with KDM it works. I tried a dozen times.
That's good to hear. That means it's a bug in gdm, which doesn't surprise me. As for understanding systemd, I don't understand it at all. I've spent the past few hours trying to understand how the display manager is launched in the first place, and I haven't been able to find anything. I know this much: /etc/init.d/rc is still being used, so the runlevels are still started the old fashioned way, at least for most things, and kdm is started through the standard /etc/init.d/xdm script. What I don't know: where rc is run from. I cannot find this, or any reference to it or inittab anywhere in the systemd source code, or in any of the configuration files. It should mean though that your old way of adding services will still work I have also seen that systemd runs everything in parallel, and there is no apparent way of disabling that, which worries me a little, since RUN_PARALLEL=yes is the source of many problems and setting it to no is a very frequent solution (or at least workaround). If this is no longer available, I wonder what will happen. Anders -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org