Description of problem: The generated file /root/anaconda-cfg.ks which results from a non-kickstart installation is not written as soon as possible. The file should be written as soon as the root filesystem has been formatted, and certainly no later than the install.log* files are created. There should even be a way for the advanced user to inspect and modify the prospective anaconda-cfg.ks kickstart file before it is used. (This would have to be even earlier, before formatting the root filesystem.) All of the installer dialogs that precede the "point of no return" should just put their results into the kickstart file in the correct syntax. The actual install must be run based on the kickstart file only. Once /root is available and /root/install.log* have been created, then there is no reason to delay further the writing of the kickstart file. Version-Release number of selected component (if applicable): anaconda-11.3.0.28 How reproducible: always Steps to Reproduce: 1. do a non-kickstart install 2. 3. Actual results: /root/anaconda-cfg.ks is not written until near the end of the install, after installing packages. Expected results: /root/anaconda-cfg.ks should be written as soon as possible, no later than the same time that /root/install.log* are created. Additional info:
The anaconda-ks.cfg file will be created much earlier in the next build of anaconda. For now we'll have to pass on having the UI generate a kickstart file that is later run, though that is certainly the direction we want to be moving in.