

You set everything to /boot because that’s the mount point of your boot partition. /dev/sda1 or whatever gets mounted to /boot
- Grub will make
/boot/EFI/<NAME>/grubx64.efiand will dump a bunch of files to/boot/grub.- For grub you edit configs in
/etc/default/gruband generate the actual configs withgrub-mkconfig
- For grub you edit configs in
- Bootctl will make
/boot/EFI/systemd/systemd-bootx64.efiand loader configs to/boot/loader- Configs for bootctl are edited directly in
/boot/loader/
- Configs for bootctl are edited directly in
- Mkinitcpio will dump
.imgfiles to/boot/
If you mount your boot partition to /boot/efi instead of just /boot, you’ll have to specify that with command line flags for each of those commands. At first that’s easy enough. grub-mkconfig and grub-install only need to be run once. I believe that the same for bootctl. mkinitcpio however runs via a pacman hook whenever you update your kernel. You’ll have to ensure that the hook doesn’t default to /boot. I don’t know how to do that though.
Better off to just accept the difference IMO. Things will “just work”.



curl command in a shell script. Use
jq,hq,gron,grepor whatever to parse output. Pipe the response to a file to cache. Use a text editor and tmux for UI. Program workflows directly into the shell script. UNICS is an IDE.tl;dr Bruno