Pre-patched kickstart tree

[Michael DeHaan]

Waller, Darrick J (US SSA) wrote:
> Sorry, I am trying to get this working with RHEL3.
>
> I will look into adding repositories to the kickstart file for RHEL5,
> that sounds really handy.
>   

FYI ... if you are using Cobbler for net installs, it can help set all 
that up for you including the repo mirroring and so forth, and will keep
track of what repos are needed by what profiles.

cobbler import --name=rhel5 --mirror=/mnt/mymounteddvd
cobbler repo add --name=epel5-x86 
--mirror=http://download.fedora.redhat.com/pub/epel/5/i386/
cobbler repo add --name=mystuff --mirror=/path/to/my/extra/stuff
cobbler repo sync
cobbler profile edit --name=nameofprofile --repos="epel5-x86 mystuff"

However I believe on IRC you said you are doing media based stuff so 
including the updates tricks really won't help you too much.
If you do have a network available at install time though, I'd recommend 
using it, as the yum integration with kickstart (EL5 and later, Fedora 6 
and later) is quite nice.

> -----Original Message-----
> From: kickstart-list-bounces at redhat.com
> [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Jesse Keating
> Sent: Monday, January 21, 2008 1:56 PM
> To: kickstart-list at redhat.com
> Subject: Re: Pre-patched kickstart tree
>
> On Mon, 21 Jan 2008 13:47:30 -0600
> "Waller, Darrick J (US SSA)" <Darrick.Waller at baesystems.com> wrote:
>
>   
>> As the subject states, I am trying to create an kickstart tree that
>> allows me to install a system with current packages, instead of older
>> packages from the downloaded ISO's that I have. I have novi installed,
>> and am able to merge the two RPMS directories that I have using hard
>> links, but when I try and kickstart a machine using this directory as
>> the install tree, I get the following error:
>>
>>  
>>
>> "That directory does not seem to contain a Red Hat Enterprise Linux
>> installation tree."
>>
>>  
>>
>> I've tried linking the 'RedHat/base' directory, thinking I needed the
>> stage2 stuff, but I still get the same error. Any advice on this, or
>> alternate methods of doing the same thing would be great.
>>     
>
>
> If this is RHEL5, why not just add a repository in your ks file that
> has all the updates in it?  Far easier than trying to reconstruct the
> install tree.
>
>