All, Before we go Gold, can the zypper dup process be updated to warn users of the possibility of needing to add init=/sbin/sysvinit to menu.lst before allowing them to proceed? I'm just talking about a simple test message that pops up somehow. I know the zypper package itself is not the way to do this because users will still be running zypper from 11.4 most likely. Is their a text file, or license file trick we could play to force a warning to the user? If not, is there a way to rush out a 11.4 update to zypper that would have it check the update repo and if its 12.1, give a warning? == my story I have a desktop machine that I upgraded a week or two ago from Tumbleweed to RC1. That went reasonably smooth. I "think" I was running systemd after that upgrade. I did NOT have a init= statement in /boot/grub/menu.lst, and I think the RC1 default was systemd. I just upgraded to RC2 via zypper up. (Note the repo was already set and I had already re-enabled a number of devel repos, so I didn't feel the need to use zypper dup.) Anyway, after the upgrade I rebooted immediately and ended up in Emergency Mode. Fortunately I knew to add init=/sbin/sysvinit. I know that will be in the release notes, but that just doesn't seem like enough of a safeguard. I don't think many of the "zypper dup" upgraders will read the release notes. Greg -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org