[haiku-bugs] Re: [Haiku] #15049: [haiku_loader] Continue booting is disabled by default
- From: "Haiku" <trac@xxxxxxxxxxxx>
- To: undisclosed-recipients: ;
- Date: Tue, 23 Mar 2021 21:59:59 -0000
#15049: [haiku_loader] Continue booting is disabled by default
-------------------------------------+----------------------------
Reporter: diver | Owner: tqh
Type: bug | Status: assigned
Priority: normal | Milestone: R1/beta3
Component: System/Boot Loader/EFI | Version: R1/Development
Resolution: | Keywords:
Blocked By: | Blocking:
Platform: All |
-------------------------------------+----------------------------
Comment (by stellarpower):
The problem is thata in EFI, they no longer have a 'boot disk' thinking.
Maybe go with that then?
If we're MBR booting, we will have started from the boot sector of a
partition, so the loader is inherently tied to the installation. If the
aim with EFI is to separate the loader and the installations a little (and
I would tend to agree with the principle, GRUB brilliantly shows how not
to do this), then would it be simpler to let the installer (eventually)
write out to a file the preferred partition GUID to boot from?
Could keep the loader generic for any installation, and alongside in the
EFI folder, a config folder with a file that lists Haiku installations in
order of priority. The first one of those found that can be booted "wins",
otherwise, the menu will be displayed. The installer can write out to this
by default, and for the user, an update to the preferred installation to
boot from would be as simple as opening this file and re-ordering or
adding an entry, be it BFS name, GPT ID or whatever (probably both would
be good)
FWIW also I think the file ought to be renamed - /boot/efi should be
shared with other OSs right, so would it be better to include "Haiku" in
the filename?
--
Ticket URL: <
https://dev.haiku-os.org/ticket/15049#comment:13>
Haiku <
https://dev.haiku-os.org>
The Haiku operating system.
Other related posts:
