On Thursday 18 January 2007 14:58, Schmidt, Jolynn wrote: > 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 Its actually more simple than that. When you add a repo to the installation, the repodata is read at the beginning. For the package names you've selected, the newest one is installed from whichever repo holds it, either the base repo preconfigured, or the added repos. This allows you to directly install the updates instead of all packages, THEN updates. Should shorten install times a bit. > 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. Yes, I do believe that is a non-iso install. The installer has access to the entire RPM set for the transaction. When doing iso based installs, rpm only has access to the headers on that particular iso, and so it builds an install order based only on that, and anaconda waits until the very end to install the "extra repo" packages. This leads to a package ordering issue, if one of the key packages has an update in your added repo. Imagine selinux having an update, and being in the extra repo. Your install starts, realizes that selinux is newer in the other repo, and thus doesn't install it from the iso. However most things ON the iso require selinux to be there, so %post scripts fail, packages don't install, whole thing goes boom. -- Jesse Keating Release Engineer: Fedora
Attachment:
pgppcjQp4Xywu.pgp
Description: PGP signature
