Michael Blandford wrote:
I have a python script that I run in the %pre section to generate
partitioning information. It dumps this information into /tmp/partition.
in the ks.cfg, I am adding %include /tmp/partition.
If the partitioning is different that what is already on the machine,
the build will stop and complain the /usr is too small. If I choose
'no' to continue, the machine reboots and starts the build again.
This time it will suceed.
It seems like the machine doesn't notice the partitioning has changed
during the build and is trying to continue using the old partitions.
This is on ia64. I am also using the same process on ia32 with RedHat
7.3 without seeing this problem.
Any thoughts on what might be wrong?
Have you tried this kickstart option for clearing all existing
partitions? I also add the option for initialising a disk if it is new ...
# clear all partitions and initialise disk if need be
clearpart --all --initlabel
hth
pantz
--
Before you criticize someone, walk a mile in their shoes ...
That way when you do criticize them, you're a mile away and you have their shoes!
