CentOS virt - Apr 2015 - Can we get a copy of ks.cfg for varous images into /root/ks.cfg?

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

I think that should be:

%post --nochroot

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

----- Original Message -----
> From: "Nico Kadel-Garcia" <nkadel at gmail.com>
> To: "Discussion about the virtualization on CentOS"
<centos-virt at centos.org>
> Sent: Saturday, 25 April, 2015 15:38:49
> Subject: [CentOS-virt] Can we get a copy of ks.cfg for varous images into
/root/ks.cfg?
> 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
> _______________________________________________
> CentOS-virt mailing list
> CentOS-virt at centos.org
> http://lists.centos.org/mailman/listinfo/centos-virt

On Sat, Apr 25, 2015 at 9:38 AM, Nico Kadel-Garcia <nkadel at gmail.com>
wrote:
> 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.
I think I would also cover the possibility of ks.cfg containing
%include statements, and copying those files to the new root as well.

jerry

On Mon, Apr 27, 2015 at 8:01 AM, Nux! <nux at li.nux.ro>
wrote:
> I think that should be:
>
> %post --nochroot
>
> --
> Sent from the Delta quadrant using Borg technology!
I think you're right, thank you!!