Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

What does it overwrite, exactly?

Each operating system has its files in their respective directories on ESP, and each operating system registers its own boot entries pointing to bootloader in these directories. With UEFI, there's nothing to overwrite, except setting the default entry.

That's not an issue, since you can both easily boot non-default entries and change, what the default entry is.



No it doesn't REMOVE the Linux's UEFI partition or files on the drive, but it sets itself to #1 in your UEFI boot list. And since their installer does not add other OSes to the Windows bootloader automatically, you have to either change your UEFI settings or your Windows BOOT.INI (for Windows MBR setups)


> No it doesn't REMOVE the Linux's UEFI partition or files on the drive, but it sets itself to #1 in your UEFI boot list

So it does what is expected from any boot loader. Installing grub does the same.

> And since their installer does not add other OSes to the Windows bootloader automatically

Which is fine; you should not chainload windows from grub either. Use ntldr for booting windows.

> you have to either change your UEFI settings

Exactly, you can change the default boot entry in your UEFI settings.

Or after POST, press a button on your keyboard for one-off boot change.

---

So what was the complain, again? Some people not using UEFI boot manager in a way it is supposed to be used?


Depending on your hardware UEFI boot manager can be a PITA. I have a Dell one where a normal boot to grub/sd-boot takes 5s. But if I want to go to the uefi boot menu for some reason it takes 30+ seconds and from what I can observe, an intermediary reboot. And I end up in some monstrous UEFI GUI with an abysmal mouse cursor behaviour.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: