Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 955 - Kickstart installation doesent allow more than 128M of swap
Summary: Kickstart installation doesent allow more than 128M of swap
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: installer
Version: 5.2
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Matt Wilson
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 1999-01-25 04:07 UTC by ahoyer
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2000-02-10 18:57:17 UTC

Attachments (Terms of Use)

Description ahoyer 1999-01-25 04:07:18 UTC
When using the kickstart option, if you need more than 128M
of swap, the kickstart setup will fail.  More than 1 swap
partition isn't allowed either.

Comment 1 Matt Wilson 1999-03-13 21:34:59 UTC
128M is a hard kernel swap limit for i386 under 2.0.x kernels.
Looking at the code, multiple swap partitions should work by doing
more than one "part swap --size 32" line.  What error do you get?

Comment 2 Matt Wilson 1999-03-13 22:11:59 UTC
Also, swap partitions up to 2 GB are supported in the next release of
Red Hat Linux.

Comment 3 ahoyer 1999-03-14 01:12:59 UTC
The idea behind the problem is that I need 256M of swap.  Reading the
howto's it says that that one can have multiple 128M swap partitions
or files to add up to a max of 2 Gb or something like that. So more
than one "part swap --size 128" didn't work for me.

Comment 4 Matt Wilson 1999-04-01 06:01:59 UTC
Dave can you please verify?

Comment 5 David Lawrence 1999-06-30 16:21:59 UTC
I have verified that on both 5.2 and 6.0 the installer ignores more
than one swap partition line in the ks.cfg file. This has been
assigned to a developer for further review.

Comment 6 Jay Turner 2000-02-10 18:56:59 UTC
This issue is resolved in the current release.

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