On 15/01/16 02:36, Nico Kadel-Garcia wrote:
> On Thu, Jan 14, 2016 at 2:37 PM, David Sommerseth> <[log in to unmask]> wrote:
>> As a rough crash-course .... checkout /root/anaconda-ks.cfg on a freshly
>> installed system.  If you want to do the exact same installation once
>> more, you copy this file to a medium or web server and provide the URI
>> to this file on the kernel command line before starting the installer.
>> If anaconda picks it up, you'll have an automated install running instantly.
> 
> Really, you don't. "anaconda-ks.cfg" is the anaconda pardsed results
> of the deployment procedure, and lacks many critical feautres of a
> robust kickstart file for PXE or other common kickstart setups.
> 
> * The default installaiton labels partitions by the DHCP or otherwise
> configured hostname, which is confusing on multiple hosts using the
> same kickstart file.
> * It comments out the disk configuration stanza.
> * It includes distinct comments and layouts from
> "system-config-kickstart" or other constructed kickstart tools.
> * It does not correctly handle multple '%pre', '%post', or '%post
> --nochroot' stanzas.

Duh!  Too long since I did that obviously.  Thanks for correcting my error!
You are absolutely right.

> If you want to use a consistent kickstart, and have each published
> host have a reference copy of its actual upstream kickstart file for
> future reference, add this stanza to your published kickstart files
> before using them.
> 
>     %pre --nochroot
>     cp /tmp/ks.cfg /mnt/sysimage/root/ks.cfg

Yupp!  That's the needed detail.


--
kind regards,

David Sommerseth