FS#28550 - [systemd-sysvcompat] Systemd needs sulogin from sysvinit
Attached to Project:
Arch Linux
Opened by Ran Benita (bluetech) - Monday, 20 February 2012, 17:23 GMT
Last edited by Dave Reisner (falconindy) - Friday, 31 August 2012, 09:54 GMT
Opened by Ran Benita (bluetech) - Monday, 20 February 2012, 17:23 GMT
Last edited by Dave Reisner (falconindy) - Friday, 31 August 2012, 09:54 GMT
|
Details
(Package version: systemd-sysvcompat 2-1)
I want to install systemd-sysvcompat (it's nice to have). It rightfully conflicts with sysvinit. However, the built-in service /lib/systemd/system/emergency.service contains this line: ExecStart=-/sbin/sulogin Which is a part of sysvinit. So with systemd-sysvcompat you will get stuck when you don't really want to get struck :) I was hit by that back in the day and even told upstream about it, but they only added a note to the README (see runtime requirements section). In fedora/etc they have sysvinit-tools for this purpose. Anyway, thought you should know. |
This task depends upon
rename the files which you replace by a link.
This has the advantage that you have sysvinit as backup (for example a cryptsetup update could break systemd mounting an encrypted disk).
I'm also inclined to believe that systemd's cryptsetup implementation would be just as broken as the binary included with cryptsetup if such a change occurred upstream... Wait for util-linux 2.22 and this solves itself.
And since you had fun doing it :) and have your way with upstream, I thought I'd hijack this bug and mention that the pidof command is also part of sysvinit, and seems to be used freely at least in some install scriptlets:
$ cd /var/abs
$ grep -Rl pidof | wc -l
154
And also in /etc/rc.d scripts. Maybe you can figure out how to port it as well?
Whatever it may be, thanks again.
Dave I'd like to use pidof in my systemd system. Thanks! :)