Bug 827138 - no information about platform-specific boot partition requirements
Summary: no information about platform-specific boot partition requirements
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora Documentation
Classification: Retired
Component: install-guide
Version: devel
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Petr Bokoc
QA Contact: Ruediger Landmann
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-31 17:32 UTC by David Lehman
Modified: 2013-07-29 17:46 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-07-29 17:46:14 UTC
Embargoed:


Attachments (Terms of Use)

Description David Lehman 2012-05-31 17:32:25 UTC
Description of problem:
The install guide appears to contain no information in the partitioning section about the various platform-specific partitioning requirements:

 GPT boot disk on BIOS needs 1MB BIOS Boot partition
 EFI boot disk needs 50-200MB EFI System partition
 PPC needs one of HFS+ /boot/efi, Apple Bootstrap, or PReP

Version-Release number of selected component (if applicable):
Fedora 17

Additional info:
It would be useful to provide descriptions of these requirements to ease the requirement for explanations in the installer itself.

Comment 1 Jack Reed 2012-11-23 00:30:47 UTC
Thanks for this, David.

The BIOS Boot requirement was already added to the Advice on Partitions list [1] as the outcome of bug 704244. It stated two other conditions besides GPT that such a partition would be required, so I believe it should suffice. Let me know if you think it's not clear enough though.

I've documented the other two items in a new list item in Advice on Partitions (see http://git.fedorahosted.org/cgit/docs/install-guide.git/commit/?id=7965709818160ccc327be6bad38e3691146d4538)


[1] http://docs.fedoraproject.org/en-US/Fedora/17/html/Installation_Guide/s2-diskpartrecommend-x86.html


Note You need to log in before you can comment on or make changes to this bug.