
\EFI\BOOT\GRUBX64.EFI on host gb250 ESP is 1,116,024 bytes and seems to be the original from when Ubuntu 18.04 was first added to the NVME's ESP /following/ Leap and TW installation, while /boot/efi/EFI/opensusetw/grubx64.efi is recent and 143,360 bytes, roughly 1/8 the size of buntu's in BOOT/. /boot/efi/EFI/debian12/grubx64.efi is more like 1/9 the size at 121,856 bytes, while /boot/efi/EFI/ubuntu22/grubx64.efi is a match for the one in BOOT/ @1,116,024 with same timestamp. https://download.opensuse.org/tumbleweed/repo/oss/EFI/BOOT/bootx64.efi is 934,024 bytes. On host ab250, \EFI\BOOT\GRUBX64.EFI matches /boot/efi/EFI/opensusetw/grubx64.efi @139,264 bytes, though with timestamps a day apart in 2020. 1-Are these grubx64.efi files created on installation specific to the installation, as was done in the MBR track on legacy partitioned disks, or simply extracted from an rpm? 2-What accounts for the vastly larger size of Ubuntu's version, or the largest one from TW in BOOT/? 3-Why is the one in BOOT from Ubuntu an apparent match to that in the ubuntu22 directory, yet those from openSUSE on BOOT either a match to one in opensusetw, or vastly larger? 4-Is it a problem, or can it be, if none of grubx64.efi or bootx64.efi or BOOTX64.EFI in /boot/efi/EFI/BOOT/ match grubx64.efi in any other directory in /boot/efi/EFI/, particularly the one that has efibootmgr priority on a normal boot? -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata