I should add that I'm basing my alphabetical argument base on the output of this script: dumphdrlist.py. Which I found during my research into the problem... Thanks, Marc Mondragon On Tue, 2004-09-14 at 10:11, Marcos A. Mondragon wrote: > Hello, > > I've been using a home built deployment server to keep my RHEL machines current with > the latest updates from RH. I've also been using it to build my new machines to the > update level we are currently as well as installing our own RPM's. I'm move the latest > RPM's into my build directory, run genhdlist and be good to go and up until the latest > U3 update this has worked very nicely for us. But something broke with the U3 release. > > I initially noticed that my installs were breaking due to the grub install failing. After > searching Google and the Red Hat mailing lists I saw a mention of a similar grub problem > which led me to this list and the message below. Searching some more I found some info > that pointed me to this solution to the hdlist being in alphabetical order: > > export PYTHONPATH=/usr/lib/anaconda > rhroot=/some/nifty/place > /usr/lib/anaconda-runtime/genhdlist $rhroot > /usr/lib/anaconda-runtime/pkgorder $rhroot i386 > $rhroot/RedHat/base/pkgorder > /usr/lib/anaconda-runtime/genhdlist --fileorder $rhroot/RedHat/base/pkgorder $rhroot > > Which seemed to be the ticket. Unfortunately my hdlist is still being created in alphabetical > order not in the proper sequential order and I've run out of clues/ideas. Does anyone have any > ideas on where I should look next? > > Thanks, > > Marc Mondragon > > > RHEL 3 genhdlist gotcha > > > > ______________________________________________________________________ > > * From: Brian Long <brilong cisco com> > > * To: anaconda-devel-list redhat com > > * Subject: RHEL 3 genhdlist gotcha > > * Date: Mon, 03 May 2004 09:38:16 -0400 > > > > ______________________________________________________________________ > > My group is just starting to support a bi-arch (i386/AMD64) kickstart > > and we found a few gotchas along the way. I figured I'd tell the rest > > of you in case it helps in any way. > > > > genhdlist must be run on the same architecture you plan to kickstart. > > For example, the genhdlist from anaconda-runtime i386 must be run for > > i386 kickstarts. The genhdlist from anaconda-runtime x86_64 must be run > > on a x86_64 machine for the bi-arch kickstart to proceed. > > > > We had been running the i386 genhdlist against a bi-arch comps.xml, but > > things were not getting installed in proper order (i386 RPMs were taking > > precedence over x86_64 RPMs). > > > > For previous releases, we've never used pkgorder since it wasn't a > > required step for NFS installs, but it appears bi-arch kickstart > > requires pkgorder AND arch-specific genhdlist. > > > > /Brian/ > > -- > > Brian Long | | | > > Americas IT Hosting Sys Admin | .|||. .|||. > > Cisco Linux Developer | ..:|||||||:...:|||||||:.. > > Phone: (919) 392-7363 | C i s c o S y s t e m s > > > > -- Marc Mondragon Fox River Financial Resources/Ritchie Capital Investments, Ltd. 2100 Enterprise Avenue Geneva, IL 60134 marcmo@xxxxxxxxxxxx
Attachment:
signature.asc
Description: This is a digitally signed message part
