FS#49784 - system unbootable after removing systemd-sysvcompat

Attached to Project: Arch Linux
Opened by Istvan Szekeres (Pistahh) - Monday, 20 June 2016, 19:51 GMT
Last edited by Dave Reisner (falconindy) - Monday, 20 June 2016, 21:07 GMT
Task Type Bug Report
Category System
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

I removed the systemd-sysvcompat library (I thought I didn't need it, native systemd command line is good enough), but after that my system didn't boot, complaining about "init" not found. I would not expect that a compatibility library is needed to be able to boot the system. I think init should be provided by the core systemd package. Or at least systemd-sysvcompat should not be just an optional dependency for systemd.


Packages:
* systemd-230-4, systemd-sysvcompat-230-4


Steps to reproduce:

1. pacman -R systemd-sysvcompat
2. reboot
3. watch as the system doesn't boot, complaining about "init" missing.
This task depends upon

Closed by  Dave Reisner (falconindy)
Monday, 20 June 2016, 21:07 GMT
Reason for closing:  Won't fix
Additional comments about closing:  Working as intended. This cannot be made a hard dependency. If you start uninstalling packages from the 'base' group, you should know what you're doing.
Comment by Dave Reisner (falconindy) - Monday, 20 June 2016, 21:06 GMT
If you want to uninstall systemd-sysvcompat, then you need to supply init= on your kernel commandline. We do this to allow for some other package to provide /sbin/init in case you don't want to run systemd (though that comes with limited warranty).

Loading...