<tt><font size=2>> From: Kamil Paral <kparal@redhat.com></font></tt>
<br><tt><font size=2>> <br>
> In the discussion about </font></tt><a href="https://bugzilla.redhat.com/show_bug.cgi?id=869978"><tt><font size=2>https://bugzilla.redhat.com/show_bug.cgi?id=869978</font></tt></a><tt><font size=2><br>
> we agreed that we should have a list of core kickstart commands that<br>
> should definitely work for a Final release.<br>
> <br>
> All the options are documented here:<br>
> </font></tt><a href=http://fedoraproject.org/wiki/Anaconda/Kickstart><tt><font size=2>http://fedoraproject.org/wiki/Anaconda/Kickstart</font></tt></a><tt><font size=2><br>
> <br>
> I tried to make a core selection. I had the following in mind:<br>
> 1. Kickstarts are used for automation, therefore the most important
<br>
> commands related to automation must work (manual intervention is not
fine).<br>
> 2. Commands which are easily work-aroundable shouldn't be part of
<br>
> the core selection.<br>
> Example: 'authconfig' kickstart command is just a wrapper around
<br>
> authconfig tool. You can issue the same command in %post and it <br>
> should do the same. If %post works, it's trivial to work around <br>
> nonfunctional authconfig kickstart command. The same applies for <br>
> 'firewall', 'group', 'user' and others, it's trivial to run it in
%post.<br>
> 3. Some commands have plenty of options. We can't really define into<br>
> the smallest detail which one of them must work and which doesn't
<br>
> have to. In this case a blocker-bug discussion is necessary to <br>
> weight the importance of the option, its usage volume and the risk
involved.<br>
> <br>
> <br>
> I arrived at three different categories of the core set:<br>
> <br>
> == Setting up installation environment ==<br>
> network<br>
> updates<br>
> keyboard<br>
> lang<br>
> rootpw<br>
> <br>
> * 'network' and 'updates' are core commands, in same cases you <br>
> really need them to start the installation.<br>
> * 'keyboard' and 'lang' might probably be worked around in %pre, but<br>
> it might be non-trivial for people. But I'm not firmly decided here.<br>
> * 'rootpw' can be worked around in %post, but I consider it pretty
<br>
> basic command to work without problems<br>
> <br>
> == Partitioning the system ==<br>
> zerombr<br>
> autopart<br>
> clearpart<br>
> part<br>
> bootloader<br>
> volgroup<br>
> logvol<br>
> <br>
> * Partitioning is pretty major function of the installer and if <br>
> doesn't work, it's just useless. I consider it core.<br>
> * LVM support might be questioned. I decided to put it here, because<br>
> LVM is the Fedora default and it might be pretty useful in some <br>
> automated installation. We can discuss it though.<br>
> * I haven't included some other partitioning commands, like 'btrfs',<br>
> 'raid', or 'multipath'. They are useful and pretty, but I don't see
<br>
> them as really core.<br>
> <br>
> == Installation process ==<br>
> install<br>
> upgrade<br>
> repo<br>
> %packages<br>
> %pre<br>
> %post<br>
> poweroff<br>
> reboot<br>
> <br>
> * 'install' and 'upgrade', because you need to be able to tell <br>
> installer which mode to use<br>
> * 'repo' because you need to set your mirror, or activate/deactive
<br>
> updates-testing, or something like that<br>
> * '%packages' because package selection is one the core functions
ofkickstart<br>
> * '%pre' and '%post' because it is often needed for some post-<br>
> install setups (setting up sshd, creating accounts etc) and also can<br>
> be used to work around broken commands<br>
> * 'poweroff' and 'reboot' because in an automated environment these
<br>
> might be very important for you. Rebooting a computer that is 1000
<br>
> miles away from you might not be an easy task.<br>
> <br>
> <br>
> It might be a bit difficult to put this into criteria, I think there<br>
> is no other way except than list the core commands. We can't say <br>
> "everything related to partitioning", because then people
would <br>
> argue "btrfs" command is included. Maybe we can create a
separate <br>
> page/subpage related to kickstart core commands and just link to it
<br>
> from the criteria document.<br>
> <br>
> Comments very welcome.</font></tt>
<br>
<br><font size=2 face="sans-serif">I make heavy use of the %include directive
which I don't see that you've mentioned anywhere. It's a rather fundamental
feature for how I use kickstarts through livecd-tools to effect dynamic
sections. I suppose I could revise my tools to create a dynamic,
yet monolith kickstart script, but at present I have everything tooled
to around a core kickstart script, numerous static helpers that get %included
and several dynamic helpers that are also %included. Thus I'd appreciate
seeing %include added to the criteria, if it's not too much of a pain.</font>
<br>
<br><font size=2 face="sans-serif">FWIW it's presently working fine for
me with my test box that was F17 originally and yum-upgraded to F18 shortly
after the branch was made. This box is running my tool that runs
livecd-tools to make custom live spins that I've been heavily testing and
developing since the branch.<br>
--<br>
John Florian</font>
<br>