[SOLVED] Why would I put the systemd hook in mkinitcpio.conf?

macaco · 2022-01-20 16:39:47

This topic is not about trouble shooting but about understanding something.

I had a look into the https://wiki.archlinux.org/title/Mkinitcpio but I am still puzzled of what would be the upside of putting the "systemd" hook. Also, will I have to remove then the "udev", "usr" and resume hook as they will be operated by "systemd"? What are the downsides?

Last edited by macaco (2022-01-23 17:32:41)

Lone_Wolf · 2022-01-23 17:14:14

The init used in the initramfs is what determines which hooks are available .

Research differences between busybox init and systemd init.

systemd has more flexibility, but busybox is from a different organisation and has a very good reputation for being reliable and stable.

Since systemd is also used for the 'real' init stage it makes some sense to use it also during initram stage.
However, how will you boot a systemd rescue shell if systemd has issues ?

Head_on_a_Stick · 2022-01-23 17:20:34

Lone_Wolf wrote:

However, how will you boot a systemd rescue shell if systemd has issues ?

The rescue shell is only omitted if the base hook is also replaced, which doesn't seem to be the OP's plan.

macaco wrote:

the upside of putting the "systemd" hook

It would allow for the systemd.volatile feature. That's all I can think of.

macaco · 2022-01-23 17:32:25

Thank you for your answers. I already set the systemd hook - no new superpowers, also no new problems - I will keep base however to avoid the issues you hinted at.

Arch Linux

#1 2022-01-20 16:39:47

[SOLVED] Why would I put the systemd hook in mkinitcpio.conf?

#2 2022-01-23 17:14:14

Re: [SOLVED] Why would I put the systemd hook in mkinitcpio.conf?

#3 2022-01-23 17:20:34

Re: [SOLVED] Why would I put the systemd hook in mkinitcpio.conf?

#4 2022-01-23 17:32:25

Re: [SOLVED] Why would I put the systemd hook in mkinitcpio.conf?

Board footer