On 24/10/2024 at 22:04, Diederik de Haas wrote:
On Thu Oct 24, 2024 at 9:08 PM CEST, Holger Wansing wrote:
here you have a device|installation, which has the legacy_boot flag
installed, but it did not work|boot despite of this. And you changed that
legacy_boot flag into a boot flag, and that made the problem go away?
(so the device boots fine).
IIUC, it booted successfully after setting the legacy_boot flag on the
/boot partition. And it still booted successfully after setting the
boot/esp flag and removing the legacy_boot flag.
So, why should we then do some work to implement the setting of the
legacy_boot flag on arm64?
I do not know what the details are between 'boot' and 'legacy_boot'.
So I can't tell if setting 'boot' would be sufficient (in all cases).
On GPT, the 'boot' flag is the same as 'esp'.
Partman sets the boot/esp flag only with method=efi, which implies that
the partition is used as ESP (FAT, mounted on /boot/efi) and cannot be
used as the root or /boot partition.
So, can I understand this, as there is no need to set the legacy_boot flag,
but just adjust the situations, where the 'boot' flag is being set?
Or do we explicitely want to support both the legacy_boot and the boot flag,
I think so, because both are needed in different use cases.
- EFI boot -> 'esp' flag on the EFI partition
- non-EFI boot -> 'legacy_boot' flag on the root/boot partition
