Bug 498730 - Request of capability to create extended partition manually
Request of capability to create extended partition manually
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Anaconda Maintenance Team
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2009-05-02 12:02 EDT by ccrisis
Modified: 2009-05-19 10:50 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-05-19 10:50:25 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description ccrisis 2009-05-02 12:02:49 EDT
Description of problem:
Not able to force creation of extended partition

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

How reproducible:

Steps to Reproduce:
1. Begin anaconda installer
2. On a blank drive, wish to create 1 primary partition and all other partitions
   on the extended partition.
3. Be unable to do so
Actual results:
Extended partition created automatically as needed by scheme

Expected results:
Extended partition created manually

Additional info:
This may be useful to plan future installations of other OSes on the primary
Comment 1 Chris Lumens 2009-05-19 10:50:25 EDT
If you use the default suggested partitioning scheme, you'll get a /boot and everything else in a partition using LVM, which leaves two partitions available for use elsewhere.  Or, you can toss everything into just a single ext3 partition if you must.

The partitioning UI in anaconda attempts to strike a balance between advanced users who want tons of options and more novice users who don't want to be overwhelmed by choices.  If you require configuration options outside what we allow, you can always create partitions manually using parted and then have anaconda use what you create.

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