Package: partman-auto Version: 168
This is a follow-up for #1078871: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1078871 Shortly it has been mentioned, that there are arm64 systems out there (for example Rockchip), which require the 'legacy_boot' flag on the root partition (or on separate /boot partition if such exists) on GPT table, to be able to boot. [1] + further messages in the bug To be able to set this 'legacy_boot' flag in a clean way and not mix this up with setting of parted's 'boot'/'esp' flag on EFI partitions, it was suggested to add a new identifier like '$legacy_boot{ }' to the pre-generated partman recipes. This identifier could then set the 'legacy_boot' flag on root/boot partitions, while the existing $bootable{ } identifier handles 'boot'/'esp' flag on EFI partitions. A new branch has been created for this proposal: [2] Alternatively, we could add a value to the existing '$bootable{ }' specifier to indicate we want to set the 'legacy_bootable' flag on GPT (and the 'boot' flag on other disk labels). E.g. $bootable{ } -> set 'boot' on non-GPT only $bootable{ legacy } -> set 'boot' on non-GPT and 'legacy_boot' on GPT What do people think about such changing the long-standing format of pre-generated recipes? Holger [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1078871#67 [2] https://salsa.debian.org/pham/partman-auto/-/commits/legacy_boot_specifier/?ref_type=heads -- Holger Wansing <hwans...@mailbox.org> PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
