Arch Linux

TheSheepGuy

Member

Registered: 2020-04-13

Posts: 47

How to update systemd-boot configured in an unconventional way

Hello. I have configured systemd-boot not quite correctly. I have all of the files needed for booting in /efi instead of some in /efi and some (the kernel files) in /boot. At the moment, every time I update I need to replace vmlinuz-linux, initramfs-linux-fallback.img, and initramfs-linux-fallback.img located in /efi with the ones in /boot which were put there by pacman.

As far as I understand, I can do this by running bootctl and setting both esp-path and boot-path options to /efi, that is "bootctl update --esp-path=/efi --boot-path=/efi". I haven't done this since I don't want to mess up my installation.

Are those options correct? Because if so, then I can add the pacman hook, as detailed on the wiki, to automate it.

Also, I wasn't sure whether to post this here or in the Kernel & Hardware section of the forums, since systemd is technically not the kernel but an application.

Scimmia

Fellow

Registered: 2012-09-01

Posts: 13,729

Re: How to update systemd-boot configured in an unconventional way

bootctl doesn't move the kernel/initramfs, and systemd-boot can't access filesystems beyond what your firmware can already access (mostly just fat).

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,361

Re: How to update systemd-boot configured in an unconventional way

If you are going to use systemd-boot in that way, just mount the ESP to /boot and be done with it.