On Thu, Mar 29, 2012 at 7:18 PM, Chris Lumens <span dir="ltr"><<a href="mailto:clumens@redhat.com">clumens@redhat.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">> How is that possible to implement with a:<br>
> 1. Show GUI, write kickstart.<br>
> 2. Process kickstart.<br>
> design?<br>
<br>
</div>We're not literally going to have one program that you use to construct<br>
a kickstart file, write the file out, and then spawn a separate program<br>
do to the processing of. We are using kickstart as the data store<br>
internally (via pykickstart) and having one program operate on it. The<br>
only writing will be towards the end of installation, where we spit out<br>
/root/anaconda-ks.cfg.<br>
<br>
A lot of these tasks like figuring out authentication information and<br>
adding extra users can be prompted for while filesystems are being<br>
created, then actually take effect and augment the ksdata after packages<br>
are laid down. They will be reflected in the final anaconda-ks.cfg.<br>
Some other tasks may not map to existing kickstart at all (yet).<br>
<span class="HOEnZb"><font color="#888888"><br>
- Chris<br>
</font></span><div class="HOEnZb"><div class="h5">--<br>
devel mailing list<br>
<a href="mailto:devel@lists.fedoraproject.org">devel@lists.fedoraproject.org</a><br>
<a href="https://admin.fedoraproject.org/mailman/listinfo/devel" target="_blank">https://admin.fedoraproject.org/mailman/listinfo/devel</a></div></div></blockquote></div><br><div>If we go for doing something like that, is there any reason to keep firstboot around? Couldn't we stuff the actions done in firstboot into anaconda with this newer asynch design?</div>