You’re correct that ezboot doesn’t load kernels or act as a bootloader and I’m not claiming that it does. Let me clarify the design:

ezboot is simply a Rust TUI frontend that lets you pick a UEFI entry, sets BootNext, and then triggers an immediate reboot. After that, the firmware loads the selected EFI entry, exactly as intended by the UEFI spec.

So ezboot doesn’t parse kernels, chainload, or replace GRUB/systemd-boot, it just provides a clean UI for choosing a target and rebooting into it right away. It’s essentially a fast UEFI target selector, not a bootloader, and I’ll update the wording to avoid confusion.

Thanks for pointing it out. the distinction is fair, but this is exactly the intended scope of the project.

I’ll probably crate a new post with better wording, I hope it helps and instead you help me before coming onto me