I’ve recently been dealing with various CentOS images on AWS, and am being forcibly reminded that the “/root/anaconda-ks.cfg” has only a passing resemblance to whatever the kickstart configuration file actually contained. But getting a copy of the actual “ks.cfg” is invaluable for updating and testing variations of the kickstart setup, especially when manipulating disk partitioning or package selection.

In particular, anaconda-ks.cfg fails to include any but the first
‘%post’ script and discards all comments that may have been in the original ks.cfg file. Coupled with the problems of system-config-kickstart, and you have no provenance for the kickstart file that was actually *used* to create a particular system.

For people building kickstart based environments, what would it take to get you to put this in your ks.cfg?

%post
cp /tmp/ks.cfg /mnt/sysimage/root/ks.cfg
%end

For older releases, ‘%end’ is not needed.

And before anyone asks, *YES* I’ve reached out to the anaconda developers in the past about this. I can try again, but in the meantime, it would really help me, and I think it would help others.

Nico Kadel-Garcia