On: No more boot loader: Please use the kernel instead

[TylerE]

Theoretically, couldn't it just write to a "boot this image next time" field (is the legacy MBR area available?) and trigger a reboot?

[adtac → TylerE]

The target image would need to reset that field so that a second reboot puts you back into the bootloader because otherwise you'll be stuck booting that image forever.

[rcxdude → adtac]

The image doesn't need to do it, that's how UEFI bootnext works: the firmware resets the flag before it loads the image.

[garaetjjte → TylerE]

Well you could change default boot entry in efivars, but if you're relying on firmware for that why not use firmware provided boot menu anyway?

[Arch-TK → TylerE]

The boot disk isn't guaranteed to be writable.

[TylerE → Arch-TK]

Even after you’ve already installed a custom boot laser to it? I mean, I agree with you in principle, but we already have the chicken - can’t existence of the egg be assumed?

[Arch-TK → TylerE]

Aside from the DVD issue mentioned in the other person's comment. I have a design for a SED OPAL based encryption setup where the system boots with a read-only boot partition and it only becomes RW as part of the initramfs running (although optionally you can just keep it RO until you need to write to it, but this requires buy-in from the package manager).

I think network booting with EFI would also suffer from a similar problem.

[yjftsjthsd-h → TylerE]

Consider a DVD that's EFI bootable; we can have whatever bootloader we want on the disc but it is not physically writable