<div dir="ltr"><div>I currently build my kickstart files in sections based on OS and then put them together with a script.</div><div>An example:<br>preamble.centos, preamble.centos7, preamble.fedora, preamble.ubuntu<br></div><div><br></div><div>Everything gets concatenated together like this</div><div><font face="monospace, monospace">cat header preamble.centos partitions.centos pre post repos.centos packages packages.centos packages.gui packages.centosgui packages.end > ks-centos6-gui.cfg</font><br></div><div><br></div><div>We use %pre to obtain info about the system like:</div><div>Which NIC to configure</div><div>Hostname</div><div>IP</div><div>MASK</div><div>Primary user</div><div>Admin user</div><div>What OU the host should be added</div><div>And the original proc/cmdline (so I can get some info like what kickstart file was originally used in the PXE boot)</div><div><br></div><div>These are all placed in /tmp/installVars as key=value</div><div><br></div><div>That file (and other logs) are moved in %post --nochroot</div><div>Then it is made available to the regular %post via the following:</div><div><div><font face="monospace, monospace">## get installVars from /root/install_logs/installVars</font></div><div><font face="monospace, monospace">while IFS="=" read -r key value; do</font></div><div><font face="monospace, monospace"> case "$key" in</font></div><div><font face="monospace, monospace"> '#'*)</font></div><div><font face="monospace, monospace"> # do nothing for comments</font></div><div><font face="monospace, monospace"> ;;</font></div><div><font face="monospace, monospace"> *)</font></div><div><font face="monospace, monospace"> eval "$key=\"$value\""</font></div><div><font face="monospace, monospace"> ;;</font></div><div><font face="monospace, monospace"> esac</font></div><div><font face="monospace, monospace">done < /root/install_logs/installVars</font></div></div><div><br></div><div><br></div>It would be GREAT if we could get user input a little easier than using our own scripts in %pre<div><br><div>I would like to +1 on the getting "<font face="monospace, monospace">%pre --log /tmp/ks-pre.log</font>" working, currently my work around is </div></div><div><div><font face="monospace, monospace">exec < /dev/tty3 > /dev/tty3 2>&1</font></div><div><font face="monospace, monospace">chvt 3</font></div><div><font face="monospace, monospace">(<br></font></div></div><div><font face="monospace, monospace">...</font></div><div><font face="monospace, monospace">) 2>&1 | /usr/bin/tee -a /tmp/ks-pre.log</font><br></div><div><font face="monospace, monospace"><br></font></div><div><font face="monospace, monospace">-Thomas</font></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Mar 2, 2016 at 8:54 AM, Chris Lumens <span dir="ltr"><<a href="mailto:clumens@redhat.com" target="_blank">clumens@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hey everyone, I've been maintaining pykickstart and kickstart support in<br>
anaconda in general for a very long time now, though I've not been very<br>
active on this list.<br>
<br>
I'm going to be looking at kickstart exclusively for the forseeable<br>
future. Specifically, my focus is going to be on widening its adoption<br>
and making it more useful to everyone. The first step in this process<br>
is information gathering.<br>
<br>
Here's what I would like to know from you guys:<br>
<br>
* How do you use kickstart right now? What work flows do you have<br>
around it? Do you generate kickstart files from some process? Do you<br>
store them in version control?<br>
<br>
* What do you do in your kickstart files? Do you have extensive %pre<br>
and %post sections? If so, what kinds of things are you doing in them?<br>
Are you doing anything that would be generally useful that I should be<br>
doing for you? Do you ever use %traceback? Do you have unusual stuff<br>
going on in %packages?<br>
<br>
* What can I do to make your life easier? What annoys you about<br>
kickstart right now? What do you wish it did? What do you wish it<br>
didn't do? Would making it more like a language be helpful? Would<br>
making it easier to define site-specific commands be helpful?<br>
<br>
I know this is all really vague stuff, but I am just starting out on<br>
this project. I don't even really know where this is going to take me<br>
yet.<br>
<br>
I'd also like to emphasize that whatever I end up doing, I want to keep<br>
compatibility with kickstart as it exists today. That's something I<br>
take seriously in pykickstart.<br>
<br>
- Chris<br>
<br>
_______________________________________________<br>
Kickstart-list mailing list<br>
<a href="mailto:Kickstart-list@redhat.com">Kickstart-list@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/kickstart-list" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/kickstart-list</a><br>
</blockquote></div><br></div>