Just saw these:
udev-171
polkit-0.101
aaa_base-11.5
filesystem-11.5
Seems to be a deep upgrade away from openSUSE-11.4 direction 12.1 ?!
No problems,
I never thought this deep upgrade would run without problems even having /run now, for I had some troubles with this deep /run change on my debian unstable box before …
This upgrade is the ultimate example Tumbleweed is a truly rolling distro. From now on Tumbleweed is not openSUSE-11.4 any more. Before one could say this is just 11.4 with a few updated apps and a new kernel. What do you think?
I have also noticed that systemd is already available. I guess that will be the next big change coming our way. 
Edit: Who wants to be the forum’s guinea pig, try it out and do a writeup??
points at swerdna 
In 12.1 milestone1 there is a boot code one can apply that forces a boot to systemd. I tried it, and I confess I did not notice any difference ! < gulp > … in my defence after starting the boot with that boot code, I ran off to grab a coffee for my wife (and myself), and my PC was up and running when I came back. I did not try anything too demanding other than internet and playing some video. I need to try systemd again with a lot more interfacing apps.
Reference Tumbleweed updates, I was looking at the differences between openSUSE-11.4, tumbleweed-11.4, and openSUSE-12.1 milestone1 in three apps: x11-xorg.conf, mesa, and the kernel (for graphic changes). As near as I can determine, 12.1 M1 with iths xorg-x11-driver-video version 7.6-68.2 is newer than tumbleweed’s stock 11.4 xorg-x11-driver-video version 7.6-53.58.1. This means 12.1 M1 has xf86-video-at-6.14.1 (where Tumbleweed has only 6.14.0) plus 12.1 has xf86-video-intel.2.15.0 and I could not see the confirmation that Tumbleweed also has that. Plus 12.1 M4 has a number of other graphic card fixes that I don’t see in Tumbleweed, but that could just be me being careless.
So its possible we may also, in a summer of updates, see some Tumbleweed graphic card updates ?
According to my Tumbleweed’s /var/log/Xorg.0.log, intel driver is at 2.14.0, as in:
32.899] (II) LoadModule: "intel"
32.900] (II) Loading /usr/lib64/xorg/modules/drivers/intel_drv.so
32.920] (II) Module intel: vendor="X.Org Foundation"
32.920] compiled for 1.9.3, module version = 2.14.0
32.920] Module class: X.Org Video Driver
32.920] ABI class: X.Org Video Driver, version 8.0
Thanks, that confirms what I suspected which is the 2.15.0 Intel driver update has yet to make it into Tumbleweed, and is speculatively (on my part) possible sometime this summer in Tumbleweed.
I note the 2.15.0 Intel driver was released the 14th of April. According to this URL : Intel Linux Graphics: 2011Q1 the xserver-1.10.0 is recommended to use with the package containing the 2.15.0 Intel driver. But as far as I can see, 12.1 M1 (which has the 2.15.0 Intel driver) does not yet have the xserver-1.10.0.
I just tried it, boot time did improve - by a massive 9 seconds!!!
73 seconds vs 82 seconds!
To ensure I understand, … did you try it in 12.1 or in 11.4 tumbleweed ?
On 12.1 (after installing systemd) I did some further 12.1 systemd testing which I documented here: The road to systemd for openSUSE 12.1 … I noted about a 10% improvement in boot speed with systemd.
I’m trying it on Tumbleweed.
So how did it go?
Everything seems to be going great so far.
Do you get the screen ‘over-write’ when booting direct to run level 3 like I observed in 12.1 with systemd ?
Does your PC have wireless ?
Yes, the overwrite can also been seen while rebooting.
No wireless on this machine.
Just tried it on a machine with wireless, won’t boot. Just sits there, no activity whatsoever.
Just tried it. Took 20 minutes to boot LOL because it decided to do fsck on my filesystems with “sysytemd-fsck [566]: /dev/sdax etc etc”.
Then I tried it again – it took 45 seconds compared with the normal 49 seconds, which is no advantage really.
BUT (and I do mean capitals) it shut off my Nvidia Twinview of two monitors.
So it’s been uninstalled for now.
Wretched thing. After removing systemd I got freeze problems when running VBox. I had to delete the root filesystem and write back a copy taken before installing systemd. That fixed it.
Try again. Wait 9 minutes !
Although having typed that … even IF waiting 9 minutes works (and it may not) that simply is NOT a practical solution.
Guess I’ll have to search to see if there is a bug report on openSUSE factory (and possibly openSUSE Tumbleweed bug report refencing the openSUSE factory bug report).
Weird, I get the same 300 second wait even if I disable WiFi via the switch.
Upon checking status of network.service, I find this, even while being connected to my network:
network.service - LSB: Configure the localfs depending network interfaces
Loaded: loaded (/etc/init.d/network)
Active: failed since Tue, 21 Jun 2011 23:34:57 +1200; 1min 55s ago
Process: 910 ExecStart=/etc/init.d/network start (code=killed, signal=TERM)
CGroup: name=systemd:/system/network.service
└ 922 /usr/sbin/NetworkManager
I was able to disable the 300 second waiting by changing the Network settings in YaST to go to the ‘traditional’ method, as opposed to using ‘network manager’.
I confess I have not had the time to search for and possible write a bug report.