Due to a number of interdependancies on packages that are not ready for
Tumbleweed, and other interactions with the system that are causing
problems for some users, I’m going to remove systemd from Tumbleweed
today to allow the developers to spend more time on getting it stable
for Factory and 12.1 instead of having to chase down problems that are
specific to Tumbleweed only.
So if you have installed systemd in Tumbleweed, I suggest you now remove
it with a simple:
zypper rm systemd
Is systemd still a no-no for tumbleweed? With 12.1 about to come out will tumbleweed be getting updates to allow systemd? If systemd is available what other changes than just installing it do we need to make?
Systemd is a part of 12.1 and 12.1 becomes the basis for Tumbleweed. Systemd works fine in 12.1 AFAIK – ergo: my guess is it will be in. (but that’s a guess, not a fact)
After the update to the 12.1 package base (I’m running Tumbleweed and tracking “current”), I can definitely verify that systemd is there and running (a few sample log entries below). I haven’t had a chance to study the logs for any anomalies or to see what’s different in YaST2 or /etc, but the system started ok after the post update boot. The change was completely transparent in the sense that I did nothing but run zypper dup and reboot when finished. No configuration changes necessary - it just worked. It remains to be seen whether we need to do anything else to fully complete the transition.
A few representative syslog entries:
Nov 16 13:51:01 tumblebumble dbus[1302]: [system] Activating via systemd: service name='org.freedesktop.login1' unit='dbus-org.freedesktop.login1.service'
Nov 16 13:51:01 tumblebumble dbus-daemon[1302]: dbus[1302]: [system] Activating via systemd: service name='org.freedesktop.login1' unit='dbus-org.freedesktop.login1.service'
Nov 16 13:51:01 tumblebumble systemd-logind[1243]: New seat seat0.
Sadly my systemd experience was a nightmare…the system booted up and would not even go into the gui…all the devices such as ethernet were down…etc…after some research I finally forced sysvinit-init to reinstall which removes systemd-init and rebooted…the system came up and worked…no idea what systemd’s problem is but in my opinion it’s no improvement…I use tumbleweed to avoid issues…
Additionally all the dialog’s say to make oss, non-oss and updates point to “openSUSE-current” vs “12.1” however oss prompt looks for a dvd file with 11.4 in the version…changing to 12.1 forces it to pull the right description file.
I don’t have a “dvd entry” and thats the error from a zypper ref at the command line. Something pulls version from the path because when it says 12.1 it correctly pulls whatever information it needs from a 12.1 version of that file which DOES exist. I found nothing in /etc/zypp to change that.
A bit off-topic here: does the repos inside openSUSE-current follow the next stable release without user interference ? I mean do i have to change pointings as i did with 11.4 repos to 12.1 ?
I’ll paste the results but I’d like to first state the error states what repo it is looking at and the file in question is NOT a rpm…it’s one of the files used by zypper to setup the repo which is why it’s in the /setup dir. The openSUSE-current has been changed back to 12.1 in this list for the OSS, Non-OSS and UPDATES repo’s. Additionally the 3 repo’s were originally added by pasting the zypper ar commands on the “upgrading to 12.1 from tumbleweed” instruction page.
| Alias | Name | Enabled | Refresh | Priority | Type | URI | Service
I’ll paste the results but I’d like to first state the error states what repo it is looking at and the file in question is NOT a rpm…it’s one of the files used by zypper to setup the repo which is why it’s in the /setup dir. The openSUSE-current has been changed back to 12.1 in this list for the OSS, Non-OSS and UPDATES repo’s. Additionally the 3 repo’s were originally added by pasting the zypper ar commands on the “upgrading to 12.1 from tumbleweed” instruction page.
| Alias | Name | Enabled | Refresh | Priority | Type | URI | Service
