Yes but by doing so you’re using the same principles as MBR boot. There’s still this coveted boot sector Windows will attempt to take back every time.
What’s nice about EFI in particular is that the motherboard loads the file from the ESP, and can load multiple of them and add them to its boot menu. Depending on the motherboard, even browse the ESP and manually go execute a .efi from it.
Which in turn makes it a lot less likely to have bootloader fuckups because you basically press F12 and pick GRUB/sd-boot and you’re back in. Previously the only fix would be boot USB and reinstall syslinux/GRUB.
I just had a bug on both of my EFI computers where they wouldn’t boot any more and a grub-install fixed it, apparently the regular update processes do not update the version on the ESP for some reason and my assumption is that it became incompatible with the modules in /boot
Adding an EFI Boot Entry for netboot.xyz after it happened on the first one really helped fix the second one though.
The reality is that a bootloader will seemingly always be needed to account for difficult BIOS’ and legacy setups (I’m looking at you, dual-booted Ubuntu 20.04).
Add comment