On Thu, Jun 23, 2011 at 01:17:17PM -0700, Roger Luedecke wrote:
On Thursday, June 23, 2011 02:17:21 AM Felix Miata wrote:
Several hours ago I did a zypper dup on a Tumbleweed system. The next several boots took an eternity each to complete, and made a mess of boot message output until I figured out systemd had been installed. The init command was broken for switching among runlevels, keyboard was producing unexpected behavior, and boot was producing messages about problems with *.services.
The fix was simple enough: 'zypper rm systemd systemd-sysvinit; zypper al systemd'.
I realize Tumbleweed is rather young and somewhat experimental, but a testbed for systemd development it should not be. That's Factory's job, right? I would have to agree. After reading this, my curiosity about Tumbleweed is gone.
Why? Tumbleweed did not switch to systemd by default, you can use 11.4 today with systemd, and if you do, and use Tumbleweed, you will get the newer version of systemd. Nothing changes otherwise, it works just as good as it did before, nothing changed. greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org