<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.2964" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=005273907-02072007><FONT face=Arial
color=#0000ff size=2>Well, first of all, you can dispense with the WS/ES/AS
redundancy. The only difference between them is what gets installed in
package groups and the redhat-release rpm. For testing binary
compatibility, you can simply test any of the WS/ES/AS versions. In fact,
depending on your kickstart, it's possible you get the exact same build from
each one (I do using our kickstart).</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=005273907-02072007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=005273907-02072007><FONT face=Arial
color=#0000ff size=2>I would probably just take my kickstart file, replace the
install source with something unique such as INSTALL_SOURCE_HERE, then do a "for
`ls /dir/of/your/install/trees`" loop using perl or sed to change the
INSTALL_SOURCE_HERE to the proper directory name and create kickstart files for
each release. You could then simply use
ks=method:/path_to_kickstarts/release.cfg.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=005273907-02072007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=005273907-02072007><FONT face=Arial
color=#0000ff size=2>It may be a bit simplistic, but it's quick and should work
just fine. Any issues you run into can be fixed in the specific release
kickstart file.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=005273907-02072007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=005273907-02072007><FONT face=Arial
color=#0000ff size=2>Although Cobbler is an excellent tool (and I highly
recommend it for anyone setting up a build infrastructure), it sounds like more
setup than you need for this project.</FONT></SPAN></DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT> </DIV>
<DIV><SPAN class=005273907-02072007><FONT face=Arial color=#0000ff
size=2>Chip</FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> kickstart-list-bounces@redhat.com
[mailto:kickstart-list-bounces@redhat.com] <B>On Behalf Of
</B>Joe_Wulf<BR><B>Sent:</B> Saturday, June 30, 2007 10:45 PM<BR><B>To:</B>
kickstart-list@redhat.com<BR><B>Subject:</B> How-to info needed for multiple
instances of RH OS's and multiple unique versions {to be
kickstarted}<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV><SPAN class=799034000-29062007>Hi. I'm a new member of the list,
recently joined about a week ago. I could really use some help regarding
kickstart.</SPAN></DIV>
<DIV><SPAN class=799034000-29062007></SPAN> </DIV>
<DIV><SPAN class=799034000-29062007>I have one physical system running
FC6. It is set up as my kickstart/NFS/DNS/DHCP server. I've a second
physical</SPAN></DIV>
<DIV><SPAN class=799034000-29062007>system, a PC with the VMware Workstation
installed and running. I use it to boot/build 'play' virtual machines from
the</SPAN></DIV>
<DIV><SPAN class=799034000-29062007>FC6 kickstart server.</SPAN></DIV>
<DIV><SPAN class=799034000-29062007></SPAN> </DIV>
<DIV><SPAN class=799034000-29062007>I've taken the /root/anaconda-ks.cfg file
from the same FC6 system and am using it, along with all the other
normal</SPAN></DIV>
<DIV><SPAN class=799034000-29062007>kickstart steps, to tailor a network-based
build of FC6. I do basically understand how to do that, and can
successfully</SPAN></DIV>
<DIV><SPAN class=799034000-29062007>build a Virtual Machine (under VMware
Workstation v6.0 on a separate computer) with FC6. Great. Now I am
cook'n.</SPAN></DIV>
<DIV><SPAN class=799034000-29062007><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=799034000-29062007>Next, I established many new directory
names, unique for each OS, established them each/all basically the
same as for</SPAN></DIV>
<DIV><SPAN class=799034000-29062007>FC6, into that same </SPAN><SPAN
class=799034000-29062007>FC6 kickstart server. The list follows for each
of the OS's I'm working with.</SPAN></DIV>
<DIV><SPAN class=799034000-29062007></SPAN> </DIV>
<DIV><SPAN class=799034000-29062007> </DIV>
<DIV>RHEL WS3u0 x32</DIV>
<DIV>RHEL WS3u1 x32</DIV>
<DIV>RHEL WS3u2 x32</DIV>
<DIV>RHEL WS3u3 x32</DIV>
<DIV>RHEL WS3u4 x32</DIV>
<DIV>RHEL WS3u5 x32</DIV>
<DIV>RHEL WS3u6 x32</DIV>
<DIV>RHEL WS3u7 x32</DIV>
<DIV>RHEL WS3u8 x32</DIV>
<DIV>RHEL WS3u9 x32 {And conceivably back to the 2.1 versions<SPAN
class=799034000-29062007>, too</SPAN>}</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>RHEL WS3u0 x64</DIV>
<DIV>RHEL WS3u1 x64</DIV>
<DIV>RHEL WS3u2 x64</DIV>
<DIV>RHEL WS3u3 x64</DIV>
<DIV>RHEL WS3u4 x64</DIV>
<DIV>RHEL WS3u5 x64</DIV>
<DIV>RHEL WS3u6 x64</DIV>
<DIV>RHEL WS3u7 x64</DIV>
<DIV>RHEL WS3u8 x64</DIV>
<DIV>RHEL WS3u9 x64 {And conceivably back to the 2.1 versions<SPAN
class=799034000-29062007>, too</SPAN>}</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>RHEL WS4u0 x32</DIV>
<DIV>RHEL WS4u1 x32</DIV>
<DIV>RHEL WS4u2 x32</DIV>
<DIV>RHEL WS4u3 x32</DIV>
<DIV>RHEL WS4u4 x32</DIV>
<DIV>RHEL WS4u5 x32</DIV>
<DIV> </DIV>
<DIV>RHEL WS4u0 x64</DIV>
<DIV>RHEL WS4u1 x64</DIV>
<DIV>RHEL WS4u2 x64</DIV>
<DIV>RHEL WS4u3 x64</DIV>
<DIV>RHEL WS4u4 x64</DIV>
<DIV>RHEL WS4u5 x64</DIV>
<DIV>xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>RHEL ES3u0 x32</DIV>
<DIV>RHEL ES3u1 x32</DIV>
<DIV>RHEL ES3u2 x32</DIV>
<DIV>RHEL ES3u3 x32</DIV>
<DIV>RHEL ES3u4 x32</DIV>
<DIV>RHEL ES3u5 x32</DIV>
<DIV>RHEL ES3u6 x32</DIV>
<DIV>RHEL ES3u7 x32</DIV>
<DIV>RHEL ES3u8 x32</DIV>
<DIV>RHEL ES3u9 x32 {And conceivably back to the 2.1 versions}</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>RHEL ES3u0 x64</DIV>
<DIV>RHEL ES3u1 x64</DIV>
<DIV>RHEL ES3u2 x64</DIV>
<DIV>RHEL ES3u3 x64</DIV>
<DIV>RHEL ES3u4 x64</DIV>
<DIV>RHEL ES3u5 x64</DIV>
<DIV>RHEL ES3u6 x64</DIV>
<DIV>RHEL ES3u7 x64</DIV>
<DIV>RHEL ES3u8 x64</DIV>
<DIV>RHEL ES3u9 x64 {And conceivably back to the 2.1 versions}</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>RHEL ES4u0 x32</DIV>
<DIV>RHEL ES4u1 x32</DIV>
<DIV>RHEL ES4u2 x32</DIV>
<DIV>RHEL ES4u3 x32</DIV>
<DIV>RHEL ES4u4 x32</DIV>
<DIV>RHEL ES4u5 x32</DIV>
<DIV> </DIV>
<DIV>RHEL ES4u0 x64</DIV>
<DIV>RHEL ES4u1 x64</DIV>
<DIV>RHEL ES4u2 x64</DIV>
<DIV>RHEL ES4u3 x64</DIV>
<DIV>RHEL ES4u4 x64</DIV>
<DIV>RHEL ES4u5 x64</DIV>
<DIV>xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx</DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV>RHEL AS3u0 x32</DIV>
<DIV>RHEL AS3u1 x32</DIV>
<DIV>RHEL AS3u2 x32</DIV>
<DIV>RHEL AS3u3 x32</DIV>
<DIV>RHEL AS3u4 x32</DIV>
<DIV>RHEL AS3u5 x32</DIV>
<DIV>RHEL AS3u6 x32</DIV>
<DIV>RHEL AS3u7 x32</DIV>
<DIV>RHEL AS3u8 x32</DIV>
<DIV>RHEL AS3u9 x32 {And conceivably back to the 2.1 versions}</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>RHEL AS3u0 x64</DIV>
<DIV>RHEL AS3u1 x64</DIV>
<DIV>RHEL AS3u2 x64</DIV>
<DIV>RHEL AS3u3 x64</DIV>
<DIV>RHEL AS3u4 x64</DIV>
<DIV>RHEL AS3u5 x64</DIV>
<DIV>RHEL AS3u6 x64</DIV>
<DIV>RHEL AS3u7 x64</DIV>
<DIV>RHEL AS3u8 x64</DIV>
<DIV>RHEL AS3u9 x64 {And conceivably back to the 2.1 versions}</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>RHEL AS4u0 x32</DIV>
<DIV>RHEL AS4u1 x32</DIV>
<DIV>RHEL AS4u2 x32</DIV>
<DIV>RHEL AS4u3 x32</DIV>
<DIV>RHEL AS4u4 x32</DIV>
<DIV>RHEL AS4u5 x32</DIV>
<DIV> </DIV>
<DIV>RHEL AS4u0 x64</DIV>
<DIV>RHEL AS4u1 x64</DIV>
<DIV>RHEL AS4u2 x64</DIV>
<DIV>RHEL AS4u3 x64</DIV>
<DIV>RHEL AS4u4 x64</DIV>
<DIV>RHEL AS4u5 x64</DIV>
<DIV>xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>RHEL AS5u0 x32</DIV>
<DIV>RHEL AS5u0 x64</DIV>
<DIV>xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx</DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV> </DIV>
<DIV>FC1 x32</DIV>
<DIV>FC2 x32</DIV>
<DIV>FC3 x32</DIV>
<DIV>FC4 x32</DIV>
<DIV>FC5 x32</DIV>
<DIV>FC6 x32</DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV>FC1 x64</DIV>
<DIV>FC2 x64</DIV>
<DIV>FC3 x64</DIV>
<DIV>FC4 x64</DIV>
<DIV>FC5 x64</DIV>
<DIV>FC6 x64</DIV>
<DIV>xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx</DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV>Fedora 7 x32</DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV>Fedora 7 x64</DIV>
<DIV>xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx</DIV>
<DIV> </DIV>
<DIV>
<DIV> </DIV>
<DIV>These are all for the Intel architecture, as that is all I have available.
I'd do other architectures too (zSeries, Itanium</DIV>
<DIV>and S/390) if someone wishes to loan me the equipment for the next year or
so. <smile></DIV>
<DIV> </DIV></DIV>
<DIV> </DIV>
<DIV><SPAN class=799034000-29062007><STRONG><U>My question is
this</U></STRONG>:</SPAN></DIV>
<DIV>How do I dynamically build OS-specific kickstart anaconda-ks.cfg files for
EACH of them without having to waste</DIV>
<DIV><SPAN class=799034000-29062007>tons</SPAN> of hours manually
installing each one<SPAN class=799034000-29062007> simply to get that one file
out of it</SPAN>???<SPAN class=799034000-29062007> I would have thought
the kickstart</SPAN></DIV>
<DIV><SPAN class=799034000-29062007>GUI would have had something to allow the
operator to 'select' which OS from the multitudes possible, that it
would</SPAN></DIV>
<DIV><SPAN class=799034000-29062007>now be looking at. If such a
capability exists, I'm unable to find it.</SPAN></DIV>
<DIV> </DIV>
<DIV>I seek to devote more of my time to<SPAN class=799034000-29062007>
developing/polishing</SPAN> the post-installation area(s) than basic OS
building.</DIV>
<DIV> </DIV>
<DIV>I have the disk resources to support hosting all the native files for
each of the OS's I've listed above.<SPAN class=799034000-29062007>
</SPAN>Additionally,</DIV>
<DIV>I've the disk resources to support hosting each of the OS's as they get
built, to include snapshots and checkpoints<SPAN
class=799034000-29062007>,</SPAN></DIV>
<DIV><SPAN class=799034000-29062007>within VMware virtual machines</SPAN>.<SPAN
class=799034000-29062007> </SPAN><SPAN
class=799034000-29062007>I</SPAN> have all the ISO's for <SPAN
class=799034000-29062007>each </SPAN>them as well. I have a 64 bit Intel system
for virtual</DIV>
<DIV>building<SPAN class=799034000-29062007> </SPAN>of OS's. I have a task which
requires<SPAN class=799034000-29062007> </SPAN>testing various capabilities
against each of the<SPAN class=799034000-29062007>se OSs</SPAN>, <SPAN
class=799034000-29062007>and uniquely</SPAN></DIV>
<DIV><SPAN class=799034000-29062007></SPAN><SPAN
class=799034000-29062007>against each of the various update/releases,
</SPAN>thus this is why I'm<SPAN class=799034000-29062007> </SPAN>approaching
kickstart from such a broad<SPAN class=799034000-29062007>
</SPAN>perspective.</DIV>
<DIV><SPAN class=799034000-29062007>I'm simply unsure on how to properly go
about it.</SPAN></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV>So, how do I manage kickstart building for any OS I wish to pick, and
have <SPAN class=799034000-29062007>the resultant anaconda-ks.cfg
file</SPAN> work</DIV>
<DIV>correctly for the chosen OS<SPAN class=799034000-29062007>, when I'm
building tons of machines 'virtually'</SPAN>?<SPAN
class=799034000-29062007> </SPAN>Do the kickstart tools in existence
today</DIV>
<DIV>facilitate this (it doesn't seem like they do)?<SPAN
class=799034000-29062007> </SPAN>If not, what manual method is<SPAN
class=799034000-29062007> </SPAN>needed? <SPAN class=799034000-29062007>
</SPAN>Is there a resource or two on</DIV>
<DIV>the net that would facili<SPAN class=799034000-29062007>ta</SPAN>te what
I'm seeking to learn?</DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV>Thank you very much in advance for your help.</DIV>
<DIV></SPAN><FONT size=-1><SPAN style="FONT-FAMILY: arial"><BR>R,<BR>-<SPAN
style="FONT-WEIGHT: bold">Joe Wulf</SPAN>, CISSP,
USN(RET)<BR></SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV></BODY></HTML>