[Bug 783842] New: Cannot get rid of systemd
https://bugzilla.novell.com/show_bug.cgi?id=783842 https://bugzilla.novell.com/show_bug.cgi?id=783842#c0 Summary: Cannot get rid of systemd Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: Linux Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: mantel@suse.com QAContact: qa-bugs@suse.de Found By: Development Blocker: --- I created a system based on openSUSE 12.2 and explicitly selected sysvinit. After the first boot, startup was controlled by systemd, but fortunately after the second boot, good old sysvinit was active. However some parts of systemd still seem to be active. For example I cannot activate NFS mounts: Sirius:/etc/init.d # insserv rpcbind insserv: Note: sysvinit service rpcbind is shadowed by systemd rpcbind.service, Forwarding request to '/bin/systemctl --no-reload enable rpcbind.service'. ln -s '/lib/systemd/system/rpcbind.service' '/etc/systemd/system/multi-user.target.wants/rpcbind.service' ln -s '/lib/systemd/system/rpcbind.socket' '/etc/systemd/system/sockets.target.wants/rpcbind.socket' insserv: Forward service request to systemctl returned error status : 512 and without rpcbind (providing portmap) no NFS mounts are possible. However systemd cannot be removed from the system since many vital parts depend on it: Sirius:/etc/init.d # rpm -e systemd-44-10.1.1.x86_64 error: Failed dependencies: libsystemd-daemon.so.0()(64bit) is needed by (installed) rpcbind-0.2.0_git201103171419-3.1.3.x86_64 libsystemd-daemon.so.0(LIBSYSTEMD_DAEMON_31)(64bit) is needed by (installed) rpcbind-0.2.0_git201103171419-3.1.3.x86_64 systemd is needed by (installed) systemd-presets-branding-basedonopensuse-12.2-3.7.1.x86_64 systemd is needed by (installed) mkinitrd-2.7.1-62.6.1.x86_64 systemd is needed by (installed) cronie-1.4.8-37.2.3.x86_64 systemd is needed by (installed) rpcbind-0.2.0_git201103171419-3.1.3.x86_64 systemd is needed by (installed) openssh-6.0p1-2.3.3.x86_64 systemd >= 44 is needed by (installed) plymouth-0.8.6.1-1.15.1.x86_64 systemd is needed by (installed) ConsoleKit-0.4.5-12.1.2.x86_64 systemd is needed by (installed) yast2-installation-2.22.10-1.1.4.noarch systemd is needed by (installed) postfix-2.8.11-2.6.1.x86_64 Please advice how I can remove systemd from my machine without losing any basic functionality. And no, using systemd is definitely NOT AN OPTION! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=783842 https://bugzilla.novell.com/show_bug.cgi?id=783842#c kk zhang <kkzhang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kkzhang@suse.com AssignedTo|bnc-team-screening@forge.pr |fcrozat@suse.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=783842 https://bugzilla.novell.com/show_bug.cgi?id=783842#c1 Frederic Crozat <fcrozat@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #1 from Frederic Crozat <fcrozat@suse.com> 2012-10-15 13:04:32 UTC --- you can't uninstall systemd, sorry. insserv is calling systemctl in addition to enabling LSB scripts, to make sure both systemd and sysv view of the services are in sync. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=783842 https://bugzilla.novell.com/show_bug.cgi?id=783842#c2 --- Comment #2 from Hubert Mantel <mantel@suse.com> 2012-10-15 13:34:46 UTC --- Well, when systemd was introduced, we were promised that we can choose between systemd and sysvinit. So this promise is no longer true. Thanks for clarification. Seems after 20 years it is now also for me time to switch to FreeBSD: If using systemd were acceptable for me, using Windows would be acceptable as well. So after two decades no SUSE founder will use SUSE (former) Linux on his private machines any longer. R.I.P. It is ironic to see that some Linux guys finally managed what thousands of Microsoft consultants never succeeded in: Destroying Linux. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=783842 https://bugzilla.novell.com/show_bug.cgi?id=783842#c3 --- Comment #3 from Frederic Crozat <fcrozat@suse.com> 2012-10-15 13:43:09 UTC --- There is no need to be so dramatic. You can still use sysvinit in 12.2 (and you couldn't either uninstall systemd in 12.1, due to the way we have to handle dependencies for packages which are shipping systemd services). And as I wrote, the error message shouldn't prevent rpcbind from being enabled under sysvinit. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com