Talk:EFI system partition: Difference between revisions

Content deleted Content added

Inline

Revision as of 02:25, 25 September 2015

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing articles
C	This article has been rated as C-class on Wikipedia's content assessment scale.
???	This article has not yet received a rating on the project's importance scale.

No ill effects?

"On Apple's Intel-based Macintosh computers, the EFI partition can be deleted without ill effect"

The system wll boot, but "without ill effects" is wrong. This is used as a location to place executables for the EFI system to perform firmware updates. See http://support.apple.com/kb/HT2434?viewlocale=en_US and http://www.rickycampbell.com/the-intel-mac-partitioning-system-efi-and-gpt/ —Preceding unsigned comment added by 92.130.118.75 (talk • contribs) 20:37, 12 April 2009

Verified and applied. the www.rickycampbell.com link has gone dead, so didn't include that. Hungry Charlie (talk) 21:02, 7 August 2009 (UTC)[reply]

Filesystem?

Which file-system should the partition be formatted to (FAT, UFS, EXT)?

Stlman (talk) 22:38, 22 November 2011 (UTC)[reply]

FAT. --Matthiaspaul (talk) 18:45, 13 August 2012 (UTC)[reply]

"Windows XP 64-bit edition" refers to Windows for IA64, not x86-64

Quote from the article: "On Windows XP 64-Bit Edition and later, access to the EFI System partition is obtained by running the mountvol /s command."

This is actually pretty obscure information and not interesting in general, instead misleading. "64-bit Edition" refers to Windows for the IA64 architecture. This command will do nothing on x86-64 architecture Windows. Executing "mountvol /?" still confusingly shows the "/s" command, but the full documentation is clear: http://technet.microsoft.com/en-us/library/cc772586.aspx

Quote: "Mounts the EFI system partition on the specified drive. Available on Itanium-based computers only."

To obtain access to this partition on x86-64 Windows, it can be assigned a drive letter in the Windows "diskpart" command line tool. — Preceding unsigned comment added by 79.239.72.139 (talk) 09:24, 23 October 2013 (UTC)[reply]

Hello there! Please be welcome to edit the article, providing appropriate references at the same time. Thank you. -- Dsimic (talk) 12:55, 23 October 2013 (UTC)[reply]

Sense of paragraph appears to be backward

"Despite the fact that the UEFI specification requires MBR partition tables to be fully supported,[3] some UEFI firmware implementations immediately switch to the BIOS-based CSM booting upon detecting certain types of partition table on the boot disk, effectively preventing UEFI booting to be performed from EFI System partitions contained on MBR-partitioned disks.[4]"

The wording should likely mean that if both an MBR and EFI System partition exist on disk, the EFI System partition should be preferred, and in (broken) some cases, it isn't.

@@ Line 28: / Line 28: @@
 : Hello there!  Please be welcome to edit the article, providing appropriate references at the same time.  Thank you. -- [[User:Dsimic|Dsimic]] ([[User talk:Dsimic|talk]]) 12:55, 23 October 2013 (UTC)
+== Sense of paragraph appears to be backward ==
+"Despite the fact that the UEFI specification requires MBR partition tables to be fully supported,[3] some UEFI firmware implementations immediately switch to the BIOS-based CSM booting upon detecting certain types of partition table on the boot disk, effectively preventing UEFI booting to be performed from EFI System partitions contained on MBR-partitioned disks.[4]"
+The wording should likely mean that if both an MBR and EFI System partition exist on disk, the EFI System partition should be preferred, and in (broken) some cases, it isn't.