Red Hat Bugzilla – Bug 6619
Install docs missing disk space and swap guidance
Last modified: 2014-08-04 18:23:05 EDT
Partitioning happens before package selection,
Package selection says how big partitions need to be.
Manuals are great at resolving this sort of thing.
There are acres of paper devoted to running druid, but
almost nothing on recommendations for how big to make the
partitions. I just got off the phone with a colleague who
has installed 6.1 several times, each time trying different
partitionings to get one to work. Clearly he's new, but the
point is that so are most users.
1. In the paper manual give the default partition sizes and
package selection for all the "canned" setups (KDE/GNOME ws,
server, etc.). Describe in words what you do and don't get
and the difference in appearance to the user.
1a. Discuss the difference between KDE and GNOME!
2. In the manual, say what the total space used by all
packages is, if all are installed, and also the total space
used by each group of packages.
3. Offer guidance on putting /usr in the same partition as /
vs. keeping them separate, and say how big each should be if
they're separate. Ditto /var and /usr/local. Recommend
that they make a symlink /var -> /home/var so that mail
isn't blown away with a reinstall. There's lots of old
fogies still using Mail and storing in their /var/spool
4. The install docs should say more about why to have a
larger or smaller swap space. Also, I saw no mention of the
128MB swap space limit. This is bad. If the limit is gone,
SAY SO, so that we don't have to spend an hour scouring the
manuals to see if it's gone or not. If it's not gone, then
definitely say so!
Thanks, and thanks for thinking of us in the IPO!
Most of these suggestions have been taken care of in Red Hat Linux 6.2/7.0
documentation. However, since these are just suggestions and not show-stopping,
must be fixed now bugs, I am closing this out. Thanks for the feedback. Other
feedback may be sent to firstname.lastname@example.org.
Thanks for the feedback. Some of these issues are addressed in our more recent
documentation; the rest, we will consider for future releases. Thanks again for