You are not logged in.
I followed the installation guide and after executing pacstrap and checking out /etc/mkinitcpio.conf on the root filesystem, I found keymap listed in the HOOKS, even though systemd is used and not busybox(udev).
That surprised me because I read on Arch Wiki that keymap is not needed as sd-vconsole does its job now, on systemd-based mkinitpcio/initramfs.
These are the default HOOKS I got:
HOOKS=(base systemd autodetect microcode modconf kms keyboard keymap sd-vconsole block filesystem fsck)On the other side, HOOKS example for encrypted disk, in the comments above the default HOOKS, seems to be "correct" -> it is the same, just without keymap, and with added sd-encrypt.
Additionally, it seems to me as if comments above did not really follow up with systemd being the new default:
- I noticed that most of the examples above in the comments are listing HOOKS configurations based on busybox(udev), there is just one using systemd (the one I just mentioned, with encryption), how is that if systemd is the new default?
- At the beginning of the big comment above, it says "'udev' is _required_ in order to automatically load modules", with no mention of systemd at all.
Last edited by Martinsos (2025-11-17 23:47:15)
Emacs, Arch Linux. Haskell, web dev
Offline
Online
Thanks, so it is indeed a mistake and the fix is already in the works!
Is there also any initiative to update the comments, or are they considered fine as they are?
Emacs, Arch Linux. Haskell, web dev
Offline
Is there also any initiative to update the comments, or are they considered fine as they are?
The installation guide links to the mkinitcpio wikip age but doesn't mention udev or other mkinitcpio hooks.
Where are the comments you feel need updating located ?
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Martinsos wrote:Is there also any initiative to update the comments, or are they considered fine as they are?
The installation guide links to the mkinitcpio wikip age but doesn't mention udev or other mkinitcpio hooks.
Where are the comments you feel need updating located ?
Sorry for not being more precise: I am talking about the comments in the code, in /etc/mkinitpcio.conf, above the HOOKS line.
There are something like 20-30 rows of comments, with couple of sentences for introduction, and then examples of different HOOKS configurations.
While reading those, they look to me like somebody forgot to update them from the old udev to new systemd approach, so I am basically asking if that is indeed so.
Last edited by Martinsos (2025-11-18 12:08:20)
Emacs, Arch Linux. Haskell, web dev
Offline
The switch is from busybox to systemd for early userspace in the initramfs stage.
Both methods have been present for atleast a decade and use udev.
The comment lines show examples and all of them still work.
If you feel there should be more examples that use systemd, file a feature request against mkinitcpio at https://gitlab.archlinux.org/archlinux/ … o/-/issues
(you'll need an account for archlinux.gitlab.org to submit a request)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline