On 2019-08-26 23:08, Warner Losh wrote: > > That's the first machine I've seen where you have to set the name like > that... there is a larger story here and we are getting incomplete reports > because it doesn't quite make sense yet... > > But there are enough reasons not to do that by default. For one thing, it > messes up rEFInd, or can. Windows doesn't install there. At most we should > prompt for older machines. We shouldn't mortgage our future to cope with a > legacy we know will sunset soon... Both Windows and Linux install \EFI\BOOT\BOOTx64.efi because that's the default that gets run if there aren't any BootXXXX variables. And yes, Windows 10 does install there. On my system I have /EFI/Boot/bootx64.efi and \EFI\Microsoft\{Boot,Recovery}, where /EFI/Boot/bootx64.efi is the same binary as bootmgfw.efi. I'm not convinced this is something that's about older systems, and that will go away. -- Rebecca CranReceived on Tue Aug 27 2019 - 03:26:04 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:21 UTC