[Bug 1255945] Missing / home from list of mandatory Directories

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1255945

Leslie Satenstein <lsatenstein at yahoo.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|CLOSED                      |MODIFIED
         Resolution|WONTFIX                     |---
           Keywords|                            |Reopened



--- Comment #2 from Leslie Satenstein <lsatenstein at yahoo.com> ---
Hi Pete.

Actually only /boot,  and / are mandatory.

If /home is omitted, it will/may be included within / with some unspecified
default size. This option is taken if automatic repartition of space is chosen
and the partition method is standard.


If swap is omitted, two options have been seen to occur.

No assignment for swap is placed within fstab. 
if with btrfs as the file system space for swap is allocated, but not assigned
and it does not appear within fstab

or 

no swap partition at all is created.

Worse

with / and /home being adjacent,  anaconda merges the two to a single
partition.

There is no documentation regarding rules when btrfs is chosen in lieu of lvm.

Test it yourself to validate my points.

Moreover
If /opt and /var are chosen as well, these are recognized by anaconda and the
space will be readjusted to accomodate these two extra directories.


What is not well documented are the options  automatic/standard, lvm, btrfs
xfs, etc. The documentation should include a matrix to explain the decisions
taken for the lvm, btrfs, and manual configurations.

Missing is what one does when more than one disk is chosen along with the
various options.

For example,   if I specify no swap on the single disk that is where Fedora 22
will be assigned, but I include a swap from a second disk, depending on
automatic/manual configuration options, I may get two swap files instead of
one.

What are the rules?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.