FS#73245 - [systemd] post-install message still recommends init=/usr/lib/systemd/systemd
Attached to Project:
Arch Linux
Opened by Sebastian Wiesner (lunaryorn) - Monday, 03 January 2022, 18:07 GMT
Last edited by Christian Hesse (eworm) - Wednesday, 09 February 2022, 18:05 GMT
Opened by Sebastian Wiesner (lunaryorn) - Monday, 03 January 2022, 18:07 GMT
Last edited by Christian Hesse (eworm) - Wednesday, 09 February 2022, 18:05 GMT
|
Details
Description:
I just noticed that the systemd post-install script still recommends to add init=/usr/lib/systemd/systemd to the kernel command line to replace sysvinit: https://github.com/archlinux/svntogit-packages/blob/8fd4bc9aea64be71f4014cb98947c649f7d41271/trunk/systemd.install#L39 Isn't this kind of obsolete these days? |
This task depends upon
Closed by Christian Hesse (eworm)
Wednesday, 09 February 2022, 18:05 GMT
Reason for closing: Implemented
Additional comments about closing: in svn
Wednesday, 09 February 2022, 18:05 GMT
Reason for closing: Implemented
Additional comments about closing: in svn
But even so, I don't think the message makes much sense these days. systemd-sysvcompat is a dependency of base, can you even not install it? I thought that everything in base is a must-have and running without any package in base is entirely unsupported. Considering this, does the recommendation to install systemd-sysvcompat make much sense? And sysvinit is long from Arch, isn't it?
Perhaps we should merge systemd-sysvcompat into systemd (and drop the message).