On Fri, Mar 30, 2012 at 09:00:16PM +0200, Per Jessen wrote: [ 8< ]
Perhaps it's better to keep it [sysvinit] until it has become largely unusable due to lack of maintenance?
At the moment both init systems have issues as stressed in this or a different thread before.¹ Please consider to add this input to the wiki page as suggested in a different reply. We need the pros and cons at one central and easy to spot location.² As long as the raised issues are not solved we can't switch to either of both only.
It doesn't hurt to have it around, and the systemd problems sofar have no doubt made many people revert to sysvinit or postpone/skip upgrading to 12.1.
Correct. Plus we have to ensure not to switch any upgrade post openSUSE 11.4 from sysvinit to systemd again. Cause those decided to go the sysvinit route very likely do intend to stay with it. Even more important we might even annoy them more by our ignorance. Cheers, Lars ¹ https://bugzilla.novell.com/show_bug.cgi?id=730193 shutdown/poweroff/reboot hangs when using sysvinit https://bugzilla.novell.com/show_bug.cgi?id=728947 insserv tries to use systemd even when booted with sysvinit https://bugzilla.novell.com/show_bug.cgi?id=727770 sysvinit: kexec says "Failed to talk to init daemon." https://bugzilla.novell.com/show_bug.cgi?id=696902 systemd as default boot handler (replacing sysvinit) for 12.1 This is the systemd meta bug https://bugzilla.novell.com/show_bug.cgi?id=749035 System hangs after entering Runlevel 0 on a sysvinit Shutdown (cause known) ² http://lists.openSUSE.org/opensuse-factory/2012-03/msg00661.html -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team + SUSE Labs SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany