Hello,
What is the advantage in having the /boot/efi on a single partition, and not /boot for example (which was the case before EFI)? In addition, the /boot/efi is a fat32.
Thank to clarify this point.
=========================================================================== Patrick DUPRÉ | | email: pdupre@gmx.com Laboratoire interdisciplinaire Carnot de Bourgogne 9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE Tel: +33 (0)380395988 ===========================================================================
On Fri, 21 Jun 2019 10:35:10 +0200 "Patrick Dupre" pdupre@gmx.com wrote:
What is the advantage in having the /boot/efi on a single partition, and not /boot for example (which was the case before EFI)? In addition, the /boot/efi is a fat32.
Thank to clarify this point.
It's not really an advantage, it's a requirement. Hardware vendors mande EFI dependent on windows, and the windows standard calls for a fat32 partition. So if linux wants to have secure boot, they have to have an efi partition that is fat32. But everything else in boot is for the OS and uses the OS filesystem, not fat32. Thus, separate /boot and /boot/efi.
On 6/21/19 1:35 AM, Patrick Dupre wrote:
What is the advantage in having the /boot/efi on a single partition, and not /boot for example (which was the case before EFI)?
UEFI doesn't boot from code stuffed into a tiny section of the MBR. Under UEFI, the non-volatile RAM holds a description of possibly several bootloaders. Each description consists of a label, and a device identifier (disk and partition, for example) where a FAT32 filesystem is expected, and a path within that filesystem. On a UEFI Fedora system, you can run "efibootmgr" to print the current list in NVRAM.
-
Gordon Messmer -
Patrick Dupre -
stan