Core6 genhdlist

[Schmidt, Jolynn]

Thanks, this is really helpful, but I would just like to clarify a couple of things.   I currently have a Core4 repository for doing ongoing yum updates so when I create the Core6 repository I will test it out with kickstart.  My updates repository has always been ftp based though, will this be an issue?  Is kickstart able to install the base from NFS and then run yum updates via ftp?

I assume I will need two lines added to the kickstart file

repo --name=myrepo --baseurl=ftp://10.1.1.1/myrepo

and

yum -y update --enablerepo=myrepo
 
I am a little confused by the iso vs. non-iso image.  We have created a Fedora/RPMS/ directory that we copied from the iso images, that directory is NFS mounted and we install from that.  Would this be considered a non-iso install?  It's the only way I have ever done it so I am not sure.
Thanks again,
Jolynn

-----Original Message-----
From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Jesse Keating
Sent: Thursday, January 18, 2007 10:24 AM
To: kickstart-list at redhat.com
Subject: Re: Core6 genhdlist

On Thursday 18 January 2007 10:03, Schmidt, Jolynn wrote:
> I have a pxe server that we use to Kickstart Core2, Core4 and now Core6
> servers.  In the past, as updates came available, I would remove the old
> RPM from the RPMS directory, replace it with the new RPM and then run
> /usr/lib/anaconda-runtime/genhdlist to update the hdlists with the new
> RPM's.  This worked great with Core2 and Core4 but is not working with
> Core6.  The PXE / Kickstart server are running on a Core2 server with
> NFS.  Is there a new way we should be updating the hdlists?

genhdlist isn't used anymore.  yum repodata is instead.  You'd need to 
recreate the repodata (using -g comps.xml to get grouping right).

Alternatively, if you're doing NFS (non-iso), ftp, or http installs, you can 
add the Updates repository in your kickstarts, it will read in data from that 
repository and interleave the updates into the install.  This way all you 
have to do is keep a local mirror of the updates repo and it's metadata.  No 
recreating anything.

Due to a design issue in anaconda/rpm/yum/whatever, this doesn't work if you 
are using NFS ISO method, or CD/DVD method.

-- 
Jesse Keating RHCE      (geek.j2solutions.net)
Fedora Legacy Team      (www.fedoralegacy.org)
GPG Public Key          (geek.j2solutions.net/jkeating.j2solutions.pub)