The new RFC for kernel installs and impact on self built kernels

mcloaked · 2026-04-08 08:46:21

Following the discussion that was linked from arch-dev-public ML, and linked to https://gitlab.archlinux.org/archlinux/ … equests/66 does anyone know if this would impact users who have built their own scripts for building custom kernels, that are installed with dracut generated initrd files in the usual /boot and /efi directories?

Would this new set of limitations prevent the installation of custom kernels using scripts developed independently from the official bootchain?

Last edited by mcloaked (2026-04-08 08:46:56)

Allan · 2026-04-08 08:51:24

A quick skim and it should have no impact, or maybe provide a standarised way to do it. It is mainly about setting rules for Arch packages. But I have not gone in depth.

mcloaked · 2026-04-12 14:38:55

The discussion on the Archlinux gitlab RFC page has been continuing - and it is not clear if the accepted standard for mounting the esp at /boot, unless there is an xbootldr partition, in which case the esp is mounted to /efi always, and the xbootldr partition to mount at /boot will be adhered to with the proposal - if that standard is not adhered to it could break some systems. So anyone with limited size of their esp, and people with dual boot machines, may possibly have broken boot files depending on how the proposals are implemented. If the proposal leads to mounting the esp at /boot it could cause problems for some users' systems. There will be users who develop their custom kernels who will be watching how this develops very carefully.

The UAPI boot partition spec is detailed at https://uapi-group.org/specifications/s … ification/ and hopefully Arch will adhere to this spec once the RFC becomes policy with appropriate decisions on how it is implemented. GRUB's use of /boot/efi does violate this policy.

Last edited by mcloaked (2026-04-12 15:18:35)

mcloaked · 2026-04-13 08:48:40

It is interesting that there are conflicting recommendations about where to mount the ESP - the linked reference to UAPI above has a different recommendation to that for kernel-install which suggests that the ESP would always be mounted at /efi irrespective of the presence of an xbootldr partition - which is much cleaner - and simpler. Then the ESP will always be mounted to /efi and if there is also an xbootldr partition then it would generally be mounted at /boot - and this would be easier to manage for almost all systems.

mcloaked · 2026-04-13 17:26:09

The proposals in the RFC linked in the first post look sensible - and using kernel-install provided by systemd should be a good way forward for installing new kernels, including for self built kernels, once the details of the proposed bootchain tools are released. In addition the same toolchain should work for adding other boot files such as memtest86 for users who already have that installed - but using the new bootchain method to create the necessary files in /efi /boot - with the details depending which boot manager is used (systemd-boot, grub, refind etc).

Last edited by mcloaked (2026-04-13 17:29:07)

Arch Linux

#1 2026-04-08 08:46:21

The new RFC for kernel installs and impact on self built kernels

#2 2026-04-08 08:51:24

Re: The new RFC for kernel installs and impact on self built kernels

#3 2026-04-12 14:38:55

Re: The new RFC for kernel installs and impact on self built kernels

#4 2026-04-13 08:48:40

Re: The new RFC for kernel installs and impact on self built kernels

#5 2026-04-13 17:26:09

Re: The new RFC for kernel installs and impact on self built kernels

Board footer