Bug 76680 - anaconda unusable on 64 memory box
anaconda unusable on 64 memory box
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
8.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Katz
Mike McLean
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-10-24 17:28 EDT by jfm2
Modified: 2007-04-18 12:47 EDT (History)
0 users

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


Attachments (Terms of Use)

  None (edit)
Description jfm2 2002-10-24 17:28:24 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i586; en-US; rv:1.0.1) Gecko/20020830

Description of problem:
More exactly it is about impossible to customize packages.  Since swap is stil
not active at this time then if you try to customize packages Linux will have to
constantly reload pages from CDROM.  For me it meant about five minutes between
the time I clicked and the system reacting

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


How reproducible:
Always

Steps to Reproduce:
1.Pass mem=64m when you are going to install
2.At package selection time try to select individual packages
3.I suggest anaconda being modified for swap actication taking place sooner if
box has only 64 megs
	

Additional info:
Comment 1 Jeremy Katz 2002-10-31 15:25:06 EST
Already done in CVS
Comment 2 Michael Fulbright 2002-12-20 12:38:25 EST
Time tracking values updated
Comment 3 Brent Fox 2003-05-25 10:51:23 EDT
I'm going through Bugzilla closing some bugs that have been marked as Modified
for some period of time.  I believe that most of these issues have been fixed,
so I'm resolving these bugs as Rawhide.  If the bug you are seeing still exists,
please reopen this report and mark it as Reopened.

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