On 06/23/2011 11:17 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?
+ 1 I really appreciate the developers work now done in Factory to test systemd and integrate it for the next 12.1 release. And it is for sure that keeping a rolling release rolling and stable requires quit some efforts. But the description http://en.opensuse.org/Tumbleweed states that it "tumbleweed is for those who wants the newest *but* stable software" and that "Tumbleweed is the newest stable and *ready for daily use*". I know that these terms can be stretched and undergo personal interpretations. But might it be possible to be a bit more conservative when it comes to big change like the recent switch to systemd and to wait for some stabilization? Just for curiosity: Is there any kind of policy (like e.g for the debian unstable -> testing package flow) which determines the package flow into Tumbleweed? In any case, thanks for the work in Tumbleweed! Cheers, Andre Massing -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org