Skip to main content
Super User

Return to Answer

Fixed links
Source Link
edit approved Aug 28, 2021 at 7:40
Marco van Hilst
edit approved Aug 28, 2021 at 7:40
Marco van Hilst
  • 103
  • 4

No, a partition is not one and the same as a file; and Wikipedia is misleading you.

That second paragraph is wrong on pretty much all points. EFI does not require any such things, and never relies upon a boot sector. If you want the gen on this, I suggest reading the actual EFI specification. It's fairly clear on what the \EFI\BOOT\BOOTxxx.EFI files are all about. They are the fallback default if nothing is configured in the Boot Manager. Normally, however, something will be configured in the Boot Manager.

EFI does not require a special partition table, it being capable of using both the old PC/AT (a.k.a. MBR or MS-DOS) partitioning scheme and the new EFI partitioning scheme. Nor are EFI boot applications specially located. Their locations are stored as paths in individual boot options. In theory, they don't even have to be on the EFI System Partition. They could in theory be on any volume whose filesystem format the firmware understands. In practice, the ESP is both the expected place that users will look at first and is guaranteed to exist by the platform and be locatable by EFI programs.

Further reading

No, a partition is not one and the same as a file; and Wikipedia is misleading you.

That second paragraph is wrong on pretty much all points. EFI does not require any such things, and never relies upon a boot sector. If you want the gen on this, I suggest reading the actual EFI specification. It's fairly clear on what the \EFI\BOOT\BOOTxxx.EFI files are all about. They are the fallback default if nothing is configured in the Boot Manager. Normally, however, something will be configured in the Boot Manager.

EFI does not require a special partition table, it being capable of using both the old PC/AT (a.k.a. MBR or MS-DOS) partitioning scheme and the new EFI partitioning scheme. Nor are EFI boot applications specially located. Their locations are stored as paths in individual boot options. In theory, they don't even have to be on the EFI System Partition. They could in theory be on any volume whose filesystem format the firmware understands. In practice, the ESP is both the expected place that users will look at first and is guaranteed to exist by the platform and be locatable by EFI programs.

Further reading

No, a partition is not one and the same as a file; and Wikipedia is misleading you.

That second paragraph is wrong on pretty much all points. EFI does not require any such things, and never relies upon a boot sector. If you want the gen on this, I suggest reading the actual EFI specification. It's fairly clear on what the \EFI\BOOT\BOOTxxx.EFI files are all about. They are the fallback default if nothing is configured in the Boot Manager. Normally, however, something will be configured in the Boot Manager.

EFI does not require a special partition table, it being capable of using both the old PC/AT (a.k.a. MBR or MS-DOS) partitioning scheme and the new EFI partitioning scheme. Nor are EFI boot applications specially located. Their locations are stored as paths in individual boot options. In theory, they don't even have to be on the EFI System Partition. They could in theory be on any volume whose filesystem format the firmware understands. In practice, the ESP is both the expected place that users will look at first and is guaranteed to exist by the platform and be locatable by EFI programs.

Further reading

added 14 characters in body
Source Link
grawity_u1686
grawity_u1686
  • 465.3k
  • 66
  • 977
  • 1.1k

No, a partition is not one and the same as a file; and Wikipedia is misleading you.

That second paragraph is wrong on pretty much all points. EFI does not require any such things, and never relies upon a boot sector. If you want the gen on this, I suggest reading the actual EFI specification. It's fairly clear on what the \EFI\BOOT\BOOTxxxxxx.EFI files are all about. They are the fallback default if nothing is configured in the Boot Manager. Normally, however, something will be configured in the Boot Manager.

EFI does not require a special partition table, it being capable of using both the old PC/AT (a.k.a. MBR or MS-DOS) partitioning scheme and the new EFI partitioning scheme. Nor are EFI boot applications specially located. Their locations are stored as paths in individual boot options. In theory, they don't even have to be on the EFI System Partition. They could in theory be on any volume whose filesystem format the firmware understands. In practice, the ESP is both the expected place that users will look at first and is guaranteed to exist by the platform and be locatable by EFI programs.

Further reading

No, a partition is not one and the same as a file; and Wikipedia is misleading you.

That second paragraph is wrong on pretty much all points. EFI does not require any such things, and never relies upon a boot sector. If you want the gen on this, I suggest reading the actual EFI specification. It's fairly clear on what the \EFI\BOOT\BOOTxxx.EFI files are all about. They are the fallback default if nothing is configured in the Boot Manager. Normally, however, something will be configured in the Boot Manager.

EFI does not require a special partition table, it being capable of using both the old PC/AT (a.k.a. MBR or MS-DOS) partitioning scheme and the new EFI partitioning scheme. Nor are EFI boot applications specially located. Their locations are stored as paths in individual boot options. In theory, they don't even have to be on the EFI System Partition. They could in theory be on any volume whose filesystem format the firmware understands. In practice, the ESP is both the expected place that users will look at first and is guaranteed to exist by the platform and be locatable by EFI programs.

Further reading

No, a partition is not one and the same as a file; and Wikipedia is misleading you.

That second paragraph is wrong on pretty much all points. EFI does not require any such things, and never relies upon a boot sector. If you want the gen on this, I suggest reading the actual EFI specification. It's fairly clear on what the \EFI\BOOT\BOOTxxx.EFI files are all about. They are the fallback default if nothing is configured in the Boot Manager. Normally, however, something will be configured in the Boot Manager.

EFI does not require a special partition table, it being capable of using both the old PC/AT (a.k.a. MBR or MS-DOS) partitioning scheme and the new EFI partitioning scheme. Nor are EFI boot applications specially located. Their locations are stored as paths in individual boot options. In theory, they don't even have to be on the EFI System Partition. They could in theory be on any volume whose filesystem format the firmware understands. In practice, the ESP is both the expected place that users will look at first and is guaranteed to exist by the platform and be locatable by EFI programs.

Further reading

These pages have moved.
Source Link
JdeBP
JdeBP
  • 27.2k
  • 1
  • 76
  • 104

No, a partition is not one and the same as a file; and Wikipedia is misleading you.

That second paragraph is wrong on pretty much all points. EFI does not require any such things, and never relies upon a boot sector. If you want the gen on this, I suggest reading the actual EFI specification. It's fairly clear on what the \EFI\BOOT\BOOTxxx.EFI files are all about. They are the fallback default if nothing is configured in the Boot Manager. Normally, however, something will be configured in the Boot Manager.

EFI does not require a special partition table, it being capable of using both the old PC/AT (a.k.a. MBR or MS-DOS) partitioning scheme and the new EFI partitioning scheme. Nor are EFI boot applications specially located. Their locations are stored as paths in individual boot options. In theory, they don't even have to be on the EFI System Partition. They could in theory be on any volume whose filesystem format the firmware understands. In practice, the ESP is both the expected place that users will look at first and is guaranteed to exist by the platform and be locatable by EFI programs.

Further reading

No, a partition is not one and the same as a file; and Wikipedia is misleading you.

That second paragraph is wrong on pretty much all points. EFI does not require any such things, and never relies upon a boot sector. If you want the gen on this, I suggest reading the actual EFI specification. It's fairly clear on what the \EFI\BOOT\BOOTxxx.EFI files are all about. They are the fallback default if nothing is configured in the Boot Manager. Normally, however, something will be configured in the Boot Manager.

EFI does not require a special partition table, it being capable of using both the old PC/AT (a.k.a. MBR or MS-DOS) partitioning scheme and the new EFI partitioning scheme. Nor are EFI boot applications specially located. Their locations are stored as paths in individual boot options. In theory, they don't even have to be on the EFI System Partition. They could in theory be on any volume whose filesystem format the firmware understands. In practice, the ESP is both the expected place that users will look at first and is guaranteed to exist by the platform and be locatable by EFI programs.

Further reading

No, a partition is not one and the same as a file; and Wikipedia is misleading you.

That second paragraph is wrong on pretty much all points. EFI does not require any such things, and never relies upon a boot sector. If you want the gen on this, I suggest reading the actual EFI specification. It's fairly clear on what the \EFI\BOOT\BOOTxxx.EFI files are all about. They are the fallback default if nothing is configured in the Boot Manager. Normally, however, something will be configured in the Boot Manager.

EFI does not require a special partition table, it being capable of using both the old PC/AT (a.k.a. MBR or MS-DOS) partitioning scheme and the new EFI partitioning scheme. Nor are EFI boot applications specially located. Their locations are stored as paths in individual boot options. In theory, they don't even have to be on the EFI System Partition. They could in theory be on any volume whose filesystem format the firmware understands. In practice, the ESP is both the expected place that users will look at first and is guaranteed to exist by the platform and be locatable by EFI programs.

Further reading

Source Link
JdeBP
JdeBP
  • 27.2k
  • 1
  • 76
  • 104