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 Don Byington Synopsys, Inc. donby lang en_US network --bootproto static --ip 198.182.34.205 --netmask 255.255.255.0 --gateway 198.182.34.1 --nameserver 198.182.34.11 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 install mouse generic3ps/2 timezone --utc US/Pacific xconfig --monitor "Dell Ultrascan 21FS" --startxonboot rootpw blah auth --enablenis --nisdomain pdxuxbre.lmc.com --nisserver 198.182.34.11 --useshadow lilo --location mbr %packages @ Networked Workstation @ Development @ X Window System @ KDE @ GNOME @ Mail/WWW/News Tools @ Multimedia Support @ Extra Documentation sysklogd net-tools netkit-base ftp fortune-mod rdate %post rdate -s 198.182.34.13 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 / /ks.mnt/post-install.pl umount /ks.mnt rmdir /ks.mnt
This issue has been forwarded to a developer for further action.
Is somebody really fixing this probelm? It's been reported since 1999-11-17 and even the rawhide still has this problem.
Issues are resolved in the latest installer (available in beta.)