Originally reported by Jonathan Wakely at https://bugzilla.redhat.com/show_bug.cgi?id=1652997
https://docs.fedoraproject.org/en-US/fedora/f29/install-guide/install/Installing_Using_Anaconda/#sect-installation-gui-manual-partitioning-recommended suggests 10gb for the / partition, this seems far too small for a modern Fedora system.
For a minimal installation, a 5 GB root partition will be sufficient. However, for most common installations which include extra packages and a graphical user interface, the root partition should be at least 10 GB; with 20 GB being sufficient for most common use cases.
On one of my F27 machines my root partition is 40gb and 80% full.
On a second F27 machine with a separate /var partition I have a 20gb root partition, which is 70% full, and another 25-40gb used in the /var partition.
Neither of those would fit in 20gb, let alone 10gb.
(I use these machines for development and package maintenance, but all sources and builds are done in /home and /var/lib/mock which are separate partitions, so I don't think my large root partitions are especially atypical.)
Should the recommendation be updated to something more realistic?
I think that anyone doing manual partitioning should already know the layout and sizes they want. Otherwise they should just be encouraged to use automatic partitioning.
Those who know what they want as an end goal, don't always know how to get the installer to bring about that end goal. So I think the install guide should focus on "how the installer works" and "how to get the installer to do what you want" rather than making any sort of recommendations. That way it's a more generic document, and easier to maintain.
We could have a quick doc, or series of them, with partitioning recommendations.
For example, this ask.fpo.org question shows a fairly common user confusion about the install-guide making a seeming suggestion to create a separate /var partition https://discussion.fedoraproject.org/t/manual-partitioning-and-var-size/33941 I think that's out of scope for the install-guide because it really requires a conversation about some fairly esoteric things that depend on use case, work load, and file system choice. And I'm convinced it just doesn't belong in the install-guide which should be more like an automobile manual. How do you use the thing. Not recommend at what speed you should drive around corners in neighborhoods.
What do you think? I'm inclined to submit a PR to remove all such recommendations and thin out the install-guide to just the nuts and bolts. Maybe add some hints about the more esoteric aspects of the installer, so that it's more pliable for users?
Login to comment on this ticket.