I've reboot several times, and in each case part 1 was for a 3.5G / as primary, part 2 was for a 256K swap as primary. All test were done by tweaking the settings for part 3 which was for /home.
1. --asprimary --size 1 --grow -> Failed with "Can't have partition out side of disk" while computing the partitions.
2. --asprimary --size 2000 -> Succeeded to partition
3. --size 1 --grow -> Succeeded to partition
It looks like the --asprimary + --grow does not work in this case. Warning - we are setting up an auto-installer for our school district to redistribute old PC's to needy families. Both of the very old PCs that I have tested so far has done the low-mem install. While I don't see any reason that this should affect the kickstart partition process, I wouldn't be surprised if this was some sort of old-school large disk issue at the bios level.
Colin,
I've reboot several times, and in each case part 1 was for a 3.5G / as primary, part 2 was for a 256K swap as primary. All test were done by tweaking the settings for part 3 which was for /home.
1. --asprimary --size 1 --grow -> Failed with "Can't have partition out side of disk" while computing the partitions.
2. --asprimary --size 2000 -> Succeeded to partition
3. --size 1 --grow -> Succeeded to partition
It looks like the --asprimary + --grow does not work in this case. Warning - we are setting up an auto-installer for our school district to redistribute old PC's to needy families. Both of the very old PCs that I have tested so far has done the low-mem install. While I don't see any reason that this should affect the kickstart partition process, I wouldn't be surprised if this was some sort of old-school large disk issue at the bios level.