ukify-generated efi file not recognized by bootctl and kernel-install about systemd

[yuwata]

-> #32855

[poettering]

we consider kernels UKIs (in context of sd-boot and its tools) that carry at least: .kernel, .osrel, .initrd. Do your kernels have that?

[equaeghe]

we consider kernels UKIs (in context of sd-boot and its tools) that carry at least: .kernel, .osrel, .initrd. Do your kernels have that?

There is no initrd. Having one seems like a strange requirement; in my 20 year's experience running linux installations (desktop, laptop, VPS), I've never needed and used one (I realize most people do use one). The generated UKIs boot fine.

Obviously, I can't expect bootctl to say anything sensible about an initrd resource that isn't there, but that seems quite unrelated to the management of UKIs with bootctl unlink and kernel-install remove. Even most of the output of bootctl list should be unaffected. Would it be possible to deal with the lack of of an .initrd resource in a more refined manner? (Bailing out only if and when an .initrd is really required, otherwise producing some ‘.initrd resource missing’ output instead of the actual output that would be generated when an initrd would be present.) It would make sd-boot and its tools more widely applicable.

Possibly related/relevant:

• https://github.com/uapi-group/specifications/blob/main/specs/unified_kernel_image.md (no .initrd required)
• uapi-group/specifications#103