[opensuse-factory] systemd on second boot?
Hello, Is it the intended behavior? When I install factory, sysvinit is used on the running system. But as soon as I reboot it, systemd is used... Also earlier it was easy to get rid of systemd, now it isn't any more: linux-0a57:~ # zypper rm systemd Loading repository data... Reading installed packages... Resolving package dependencies... The following packages are going to be REMOVED: acpid autoyast2-installation NetworkManager NetworkManager-kde4-libs NetworkManager-openvpn NetworkManager-openvpn-kde4 NetworkManager-pptp NetworkManager-pptp-kde4 NetworkManager-vpnc NetworkManager-vpnc-kde4 patterns-openSUSE-base patterns-openSUSE-enhanced_base patterns-openSUSE-games patterns-openSUSE-imaging patterns-openSUSE-imaging_opt patterns-openSUSE-kde4 patterns-openSUSE-kde4_basis patterns-openSUSE-kde4_imaging patterns-openSUSE-non_oss patterns-openSUSE-non_oss_opt patterns-openSUSE-sw_management_kde4 patterns-openSUSE-x11 patterns-openSUSE-x11_opt patterns-openSUSE-yast2_basis patterns-openSUSE-yast2_install_wf plasmoid-networkmanagement systemd yast2-add-on yast2-backup yast2-installation yast2-update 31 packages to remove. After the operation, 12.3 MiB will be freed. Continue? [y/n/?] (y): Bye, CzP -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Thu, Sep 15, 2011 at 03:54:28PM +0200, Peter Czanik wrote:
Hello, Is it the intended behavior? When I install factory, sysvinit is used on the running system. But as soon as I reboot it, systemd is used...
Yes, that is the default right now.
Also earlier it was easy to get rid of systemd, now it isn't any more:
linux-0a57:~ # zypper rm systemd Loading repository data... Reading installed packages... Resolving package dependencies...
The following packages are going to be REMOVED: acpid autoyast2-installation NetworkManager NetworkManager-kde4-libs NetworkManager-openvpn NetworkManager-openvpn-kde4 NetworkManager-pptp NetworkManager-pptp-kde4 NetworkManager-vpnc NetworkManager-vpnc-kde4 patterns-openSUSE-base patterns-openSUSE-enhanced_base patterns-openSUSE-games patterns-openSUSE-imaging patterns-openSUSE-imaging_opt patterns-openSUSE-kde4 patterns-openSUSE-kde4_basis patterns-openSUSE-kde4_imaging patterns-openSUSE-non_oss patterns-openSUSE-non_oss_opt patterns-openSUSE-sw_management_kde4 patterns-openSUSE-x11 patterns-openSUSE-x11_opt patterns-openSUSE-yast2_basis patterns-openSUSE-yast2_install_wf plasmoid-networkmanagement systemd yast2-add-on yast2-backup yast2-installation yast2-update
31 packages to remove. After the operation, 12.3 MiB will be freed. Continue? [y/n/?] (y):
Don't do that, just change your boot command line to not use systemd and you should be fine. But, systemd is enabled for a reason right now. Are there problems with it that cause it to not work for you? If so, have you filed bugs about them? greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 09/15/2011 04:10 PM, Greg KH wrote:
On Thu, Sep 15, 2011 at 03:54:28PM +0200, Peter Czanik wrote:
Hello, Is it the intended behavior? When I install factory, sysvinit is used on the running system. But as soon as I reboot it, systemd is used... Yes, that is the default right now. Ooops.
Don't do that, just change your boot command line to not use systemd and you should be fine.
But, systemd is enabled for a reason right now. Are there problems with it that cause it to not work for you? If so, have you filed bugs about them? I exchanged some e-mails about it here: syslog error messages are "eaten" by systemd, so if I edit syslog-ng.conf and have a typo, then it does not start and there is no error message on screen. And similar
So append "init=/sbin/init" problems. systemd and syslog-ng upstream are discussing it right now, that's why no bug reports. Also: not yet filed: X does not start automagically when systemd is used. At least this happened with both a GNOME and a KDE based installation on todays' factory. It works fine with sysvinit... Bye, CzP -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Thursday 15 September 2011, Greg KH wrote:
On Thu, Sep 15, 2011 at 03:54:28PM +0200, Peter Czanik wrote:
linux-0a57:~ # zypper rm systemd Loading repository data...
Don't do that, just change your boot command line to not use systemd and you should be fine.
You can't deinstall systemd? My plan was to blacklist the systemd package before upgrading my systems one day. This will not work neither? cu, Rudi -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Am Donnerstag, 15. September 2011, 16:41:03 schrieb Ruediger Meier:
On Thursday 15 September 2011, Greg KH wrote:
On Thu, Sep 15, 2011 at 03:54:28PM +0200, Peter Czanik wrote:
linux-0a57:~ # zypper rm systemd Loading repository data...
Don't do that, just change your boot command line to not use systemd and you should be fine.
You can't deinstall systemd? My plan was to blacklist the systemd package before upgrading my systems one day. This will not work neither?
No, and systemd package won't do harm either Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Thursday 15 September 2011, Stephan Kulow wrote:
Am Donnerstag, 15. September 2011, 16:41:03 schrieb Ruediger Meier:
You can't deinstall systemd? My plan was to blacklist the systemd package before upgrading my systems one day. This will not work neither?
No, and systemd package won't do harm either
So then doing zypper dup on 11.4 it will neither deinstall sysvinit nor using systemd per default? cu, Rudi -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Am Donnerstag, 15. September 2011, 16:55:27 schrieb Ruediger Meier:
On Thursday 15 September 2011, Stephan Kulow wrote:
Am Donnerstag, 15. September 2011, 16:41:03 schrieb Ruediger Meier:
You can't deinstall systemd? My plan was to blacklist the systemd package before upgrading my systems one day. This will not work neither?
No, and systemd package won't do harm either
So then doing zypper dup on 11.4 it will neither deinstall sysvinit nor using systemd per default?
It won't deinstall sysvinit, but will use systemd per default - because it's the default and as such better supported. But with 12.1 you will be able to switch back easily. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Thursday 15 September 2011, Stephan Kulow wrote:
Am Donnerstag, 15. September 2011, 16:55:27 schrieb Ruediger Meier:
On Thursday 15 September 2011, Stephan Kulow wrote:
Am Donnerstag, 15. September 2011, 16:41:03 schrieb Ruediger Meier:
You can't deinstall systemd? My plan was to blacklist the systemd package before upgrading my systems one day. This will not work neither?
No, and systemd package won't do harm either
So then doing zypper dup on 11.4 it will neither deinstall sysvinit nor using systemd per default?
It won't deinstall sysvinit, but will use systemd per default - because it's the default and as such better supported. But with 12.1 you will be able to switch back easily.
Hm it's really pity that deinstalling systemd is not supported. Synchronizing /etc/zypp/locks between my machines is much easier than /etc/sysconfig/bootloader which may differ on different hardware. BTW for example why acpid requires systemd? Or why patterns-openSUSE-games and patterns-openSUSE-non_oss should care about which boot system is installed? I know that systemd is comming for sure. But wouldn't it be possible at least to review all these strange dependencies again? cu, Rudi -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Am Donnerstag, 15. September 2011, 17:44:43 schrieb Ruediger Meier:
I know that systemd is comming for sure. But wouldn't it be possible at least to review all these strange dependencies again? I'm sure it's possible to review them. I won't block you.
Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Thursday 15 September 2011, Greg KH wrote:
On Thu, Sep 15, 2011 at 03:54:28PM +0200, Peter Czanik wrote:
Hello, Is it the intended behavior? When I install factory, sysvinit is used on the running system. But as soon as I reboot it, systemd is used...
Yes, that is the default right now.
Even I've tried a fresh install from openSUSE-DVD-Build0250. I don't see systemd is not used per default here or am I too blind? $ lsof -p 1 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME init 1 root cwd DIR 253,2 4096 2 / init 1 root rtd DIR 253,2 4096 2 / init 1 root txt REG 253,2 40768 5968 /sbin/init [...] $ rpm -q --whatprovides /sbin/init sysvinit-2.88+-59.2.x86_64 At which point should the magic happen to select between starting init or systemd? cu, Rudi -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Am Freitag, 16. September 2011 schrieb Ruediger Meier:
On Thursday 15 September 2011, Greg KH wrote:
On Thu, Sep 15, 2011 at 03:54:28PM +0200, Peter Czanik wrote:
Hello, Is it the intended behavior? When I install factory, sysvinit is used on the running system. But as soon as I reboot it, systemd is used...
Yes, that is the default right now.
Even I've tried a fresh install from openSUSE-DVD-Build0250.
I don't see systemd is not used per default here or am I too blind?
$ lsof -p 1 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME init 1 root cwd DIR 253,2 4096 2 / init 1 root rtd DIR 253,2 4096 2 / init 1 root txt REG 253,2 40768 5968 /sbin/init [...]
$ rpm -q --whatprovides /sbin/init sysvinit-2.88+-59.2.x86_64
At which point should the magic happen to select between starting init or systemd?
In the grub boot menu - in build250 the default is sysvinit, but f5 will change it. At ~270 the default is systemd Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Friday 16 September 2011, Stephan Kulow wrote:
Am Freitag, 16. September 2011 schrieb Ruediger Meier:
At which point should the magic happen to select between starting init or systemd?
In the grub boot menu - in build250 the default is sysvinit, but f5 will change it. At ~270 the default is systemd
Ok, even I've made a zypper dup against factory. First reboot was "successful" but without any logging output on my splash=native console. Also it got into runlevel 5 instead of my default runlevel 3. Furthermore while booting it messed up /etc without asking me: factory:/etc/systemd # git st # On branch master # Changes to be committed: # (use "git reset HEAD <file>..." to unstage) # # new file: system/klogd.service # new file: system/multi-user.target.wants/syslog.service # # Changes not staged for commit: # (use "git add/rm <file>..." to update what will be committed) # (use "git checkout -- <file>..." to discard changes in working directory) # # deleted: ../init.d/rc2.d/K07syslog # deleted: ../init.d/rc2.d/K08earlysyslog # deleted: ../init.d/rc2.d/S01earlysyslog # deleted: ../init.d/rc2.d/S03syslog # deleted: ../init.d/rc3.d/K07syslog # deleted: ../init.d/rc3.d/K08earlysyslog # deleted: ../init.d/rc3.d/S01earlysyslog # deleted: ../init.d/rc3.d/S03syslog # deleted: ../init.d/rc5.d/K07syslog # deleted: ../init.d/rc5.d/K08earlysyslog # deleted: ../init.d/rc5.d/S01earlysyslog # deleted: ../init.d/rc5.d/S03syslog Then I've tried the next reboot immediately (without doing anything before)... Now I see my black console hanging with blinking cursur. So I think there is a good reason to blacklist systemd package. cu, Rudi -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Le vendredi 16 septembre 2011 à 21:48 +0200, Rüdiger Meier a écrit :
On Friday 16 September 2011, Stephan Kulow wrote:
Am Freitag, 16. September 2011 schrieb Ruediger Meier:
At which point should the magic happen to select between starting init or systemd?
In the grub boot menu - in build250 the default is sysvinit, but f5 will change it. At ~270 the default is systemd
Ok, even I've made a zypper dup against factory.
First reboot was "successful" but without any logging output on my splash=native console. Also it got into runlevel 5 instead of my default runlevel 3.
Furthermore while booting it messed up /etc without asking me:
This is not systemd but syslog-service package. It should probably put generated files in /run and not in /etc (and not change sysv dependencies).
factory:/etc/systemd # git st # On branch master # Changes to be committed: # (use "git reset HEAD <file>..." to unstage) # # new file: system/klogd.service # new file: system/multi-user.target.wants/syslog.service # # Changes not staged for commit: # (use "git add/rm <file>..." to update what will be committed) # (use "git checkout -- <file>..." to discard changes in working directory) # # deleted: ../init.d/rc2.d/K07syslog # deleted: ../init.d/rc2.d/K08earlysyslog # deleted: ../init.d/rc2.d/S01earlysyslog # deleted: ../init.d/rc2.d/S03syslog # deleted: ../init.d/rc3.d/K07syslog # deleted: ../init.d/rc3.d/K08earlysyslog # deleted: ../init.d/rc3.d/S01earlysyslog # deleted: ../init.d/rc3.d/S03syslog # deleted: ../init.d/rc5.d/K07syslog # deleted: ../init.d/rc5.d/K08earlysyslog # deleted: ../init.d/rc5.d/S01earlysyslog # deleted: ../init.d/rc5.d/S03syslog
Then I've tried the next reboot immediately (without doing anything before)... Now I see my black console hanging with blinking cursur.
So I think there is a good reason to blacklist systemd package.
Or fill a bug against syslog.
--
Frederic Crozat
Am Donnerstag, 15. September 2011, 15:54:28 schrieb Peter Czanik:
Hello, Is it the intended behavior? When I install factory, sysvinit is used on the running system. But as soon as I reboot it, systemd is used... Also earlier it was easy to get rid of systemd, now it isn't any more:
Yes, systemd should be used by default on every boot, but this is somehow broken. The default change is happening in the bootloader, not by packaging. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (6)
-
Frederic Crozat -
Greg KH -
Peter Czanik -
Ruediger Meier -
Rüdiger Meier
-
Stephan Kulow