On 03/02/2018 10:27 PM, Frank Scheiner wrote: >> On x86, it will automatically use GPT if the machine is booted in EFI mode. >> On sparc64, we would normally just switch to GPT if the machine supports GPT. > > I understand. Then it's safe to just use the subarch to select how GRUB2 > should be installed, although it's really not less complex than using the > variable.
The thing is - I don't want to deviate the code too much from what's doing on the other architectures. I don't necessarily disagree with you, but I just want to go along with the other architectures for the time being. However, if you're really concerned about the issue, I think we should discuss this in a separate thread and also involve the debian-boot mailing list so that we can find a common solution for all architectures. >> I know you try to make the most compatible design to fit all use cases, but >> I don’t think we should support such edge cases when debian-installer doesn’t >> support it on other platforms. > > Ok, makes sense. We can still address this once the other stuff works. You definitely have a point though that there can be cases where the current code will most likely fail. Maybe it's a good idea to perform some tests with such setups on x86 (e.g. having MBR partitioning and then booting the machine in EFI mode and keeping the MBR setup) and observe what debian-installer does. PS: I wrote "MFT" in my previous mail. I meant MBR, of course. MFT is part of NTFS. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913