[haiku-bugs] Re: [Haiku] #14967: Add EFI platform support to makebootable
- From: "Haiku" <trac@xxxxxxxxxxxx>
- To: undisclosed-recipients: ;
- Date: Wed, 05 Feb 2020 14:17:40 -0000
#14967: Add EFI platform support to makebootable
--------------------------------------+----------------------------
Reporter: kallisti5 | Owner: nobody
Type: task | Status: new
Priority: normal | Milestone: Unscheduled
Component: System/Boot Loader/EFI | Version: R1/Development
Resolution: | Keywords: makebootable
Blocked By: | Blocking:
Has a Patch: 0 | Platform: All
--------------------------------------+----------------------------
Comment (by X512):
Replying to [comment:8 tqh]:
I think you should read the specs. The correct way is to add a boot
option to the firmware. And there are no write count limits. There was a
firmware bug that if nvram got full the computer don't boot. That's why
Linux limits to 50% usage of NVRAM.
I think we should follow specs and best practices, not just 'This works
for me'.
Reality is more important than specs. Most firmware are made only for
booting Windows and not tested for anything else; altering firmware
settings may be dangerous and make PC permanently unbootable in worst
case. Firmware settings are also non obvious and hard to manage. For
example it is difficult to delete boot entry, there are no such option in
my EFI firmware built-in interface. I don't want to collect orphan boot
entries after testing OS. It is also non-obvious which boot entry
corresponds to which disk and EFI application (built-in interface don't
show it).
Is there examples of PC that don't detect partitions with
`EFI/BOOTX64/bootx64.efi` or don't allow to setup automatic boot from this
partitions? In practice `bootx64.efi` is basically same as first 512 bytes
of disk in BIOS.
--
Ticket URL: <
https://dev.haiku-os.org/ticket/14967#comment:9>
Haiku <
https://dev.haiku-os.org>
The Haiku operating system.
Other related posts:
