Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 7091 - --grow and --maxsize don't work with 6.1 KickStart
--grow and --maxsize don't work with 6.1 KickStart
Product: Red Hat Linux
Classification: Retired
Component: installer (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Matt Wilson
Depends On:
  Show dependency treegraph
Reported: 1999-11-17 18:51 EST by Don
Modified: 2008-05-01 11:37 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-02-22 12:05:11 EST
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 Don 1999-11-17 18:51:28 EST
On a 4G drive the partitions defined in the ks.cfg on the boot floppy are
as such;
clearpart --all
part / --size 150
part /var --size 80 --grow --maxsize 100
part /usr --size 700 --grow --maxsize 800
part swap --size 128 --grow --maxsize 200
part /tmp --size 100 --grow

What I get is;
Filesystem           1k-blocks      Used Available Use% Mounted on
/dev/sda5               155545     43856    103659  30% /
/dev/sda7               388693        32    368582   0% /tmp
/dev/sda1              2727572    645024   1943992  25% /usr
/dev/sda8               326682      9582    300234   3% /var

Filename                        Type            Size    Used    Priority
/dev/sda6                       partition       522072  0       -1

The / partition is correct, however everything else is skewed slightly. Not
that it seemed to choose sizes correctly, I just don't understand why it
didn't stop with a 100M /var, an 800M /usr, a 200M swap and give the rest
to /tmp.

Is there an explination behind this? Below is the ks.cfg in its entirety.

Thanks for the help,


Don Byington
Synopsys, Inc.

lang en_US
network --bootproto static --ip --netmask
--gateway --nameserver
nfs --server pdxuxfs16.pdxuxbre.lmc.com --dir /q-bigfs/KickStart/6.1
keyboard us
zerombr yes
clearpart --all
part / --size 150
part /var --size 80 --grow --maxsize 100
part /usr --size 700 --grow --maxsize 800
part swap --size 128 --grow --maxsize 200
part /tmp --size 100 --grow
mouse generic3ps/2
timezone --utc US/Pacific
xconfig --monitor "Dell Ultrascan 21FS" --startxonboot
rootpw blah
auth --enablenis --nisdomain pdxuxbre.lmc.com --nisserver
lilo --location mbr
@ Networked Workstation
@ Development
@ X Window System
@ Mail/WWW/News Tools
@ Multimedia Support
@ Extra Documentation
rdate -s
echo "Synopsys NCS Beaverton Kickstart-installed Red Hat Linux `/bin/date`"
> /etc/motd
mkdir /ks.mnt
mount pdxuxfs16.pdxuxbre.lmc.com:/q-bigfs/KickStart/6.1 /ks.mnt
cd /
umount /ks.mnt
rmdir /ks.mnt
Comment 1 Jay Turner 1999-11-29 13:51:59 EST
This issue has been forwarded to a developer for further action.
Comment 2 Hannu Martikka 2000-01-27 05:05:59 EST
Is somebody really fixing this probelm?
It's been reported since 1999-11-17 and even the rawhide still has this problem.
Comment 3 Jay Turner 2000-02-22 12:04:59 EST
Issues are resolved in the latest installer (available in beta.)

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