Mageia forum

How do I uninstall safely systemd and install sysvinit?
As a home user I'm not seeing systemd advantage and has many bugs and is not fully integrated with MCC! Could help me?

Through a tip I get the replacement with the commands below:

Code: Select all

# urpmi sysvinit-legacy
# urpmi sysvinit-legacy-tools
# rpm -e --nodeps systemd
# rpm -e --nodeps systemd-units
# rpm -e --nodeps systemd-sysvinit
# rpm -e --nodeps lib64systemd-daemon0
# rpm -e --nodeps lib64systemd-id1280
# rpm -e --nodeps lib64systemd-journal0
# rpm -e --nodeps lib64systemd-login0


However the system has broken dependencies.

Code: Select all

# yum check
1: 2-6. the underlying-mga2. x86_64 has missing requirements systemd
cups-common-5.1.1.5.2-mga2. x86_64 has missing requirements libsystemd-daemon.so. 0 (64 bit)
polkit-0.104-4. mga2. x86_64 has missing requirements of systemd-units
rpm-helper-0.24.10-1. mga2. noarch has missing requirements systemd-units
udisks-1.0.4-6. mga2. x86_64 has missing requirements of systemd-units
Error: check all

How do I resolve these dependencies broken? How is supported upgrade Mageia 1 for Mageia 2 and one can continue using sysvinit-legacy, which packages need to replace to not ask systemd dependencies?

You should not use --nodeps except in a few, very specialist cases. Dependences are added for a reason, so do not try to outsmart the system.

In this case if you want to boot with sysvinit, you do not need to removed systemd or systemd-units or any of the libraries. It's totally unnecessary. The only package you need to remove is systemd-sysvinit and replace it with sysvinit-legacy.

All that said, please don't do this!! sysvinit, while still supported officially is much less supported in practice.

Not seeing the "advantages" is one thing but integration into MMC should fine generally so I'm not sure what issues you're referring to. If you are "just a home user" then you really shouldn't be trying to fiddle about with the recommended paths for boot and init systems!!!

I need that all services are configured by drakxservices. In Mageia 1 everything works. In Mageia 2 some services do not work and do not appear in the list of configuration such as TOR!
It is tiring for a home user to be editing services on the nail. So I like to use drakxservices.

Should provide sysvinit 2.88 on Mageia as an alternative for those who have problems with systemd.

So because one service (in your particular example) is not listed in MCC, you don't file a bug for the missing integration, but try to exchange the whole init system?
Seems like shooting sparrows with cannons to me ...

doktor5000,

I believe that I be very reasonable. I just replace the init, most people when things do not work in a distro replace distro.
I really like mageia, I post bugs and do reviews for it to be better.