Bug 122 - Documentation Problems
Documentation Problems
Product: Red Hat Linux
Classification: Retired
Component: distribution (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Documentation
Depends On:
  Show dependency treegraph
Reported: 1998-11-18 09:47 EST by enorris
Modified: 2008-05-01 11:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 1999-05-23 11:08:56 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 enorris 1998-11-18 09:47:37 EST
Red Hat Server V5.2 requires 256mb for / and /var and 512mb
for /usr and /home. In Section 2.7.5 the stated sizes are
too small. You may want to update this section to reflect
Section 2.6.2.

A year ago I started with V5.0 and followed the directions
in the "How Many Partitions?" section. I created /, /var,
/usr, and /home partitions. I did a full install. I was able
to successfully upgrade to V5.1, but the V5.2 upgrade fails
because I don't have enough disk space in my /var partition.
You may want to put a warning someplace in the

PS. Make a Doumentation "component" for Bugzilla!
Comment 1 David Lawrence 1998-11-18 11:34:59 EST
I have verified that the documentation in the manual needs to be more
clear on the different sizing issues as related to server installs
versus custom installs. The server install requires partitions to be a
fixed size where as the custom option allows you to make partitions of
smaller sizes depending on what the user wants.
Comment 2 Preston Brown 1999-03-18 10:20:59 EST
Has documentation resolved this in the latest iteration of the
installation manual?  If so, please close this bug.

------- Email Received From  "Ed Norris, CISSP" <enorris@gte.com> 03/18/99 10:34 -------
Comment 3 Ed Bailey 1999-05-23 11:08:59 EDT
We've done a bit of a re-write on this section.  That, in conjunction
with RPM's new disk space tracking hopefully mean that this issue will
no longer be a problem...

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