I'm trying to build a custom installation CD of current, bug-fixed RH6.2 (necessary software is tested on 6.2, not on 7.1), and am encountering some obstacles. Basically, I need to create an automated install (using kickstart) that I can pass onto someone else to build 30+ boxes (and reinstall if h/w problems occur in time). There's a couple of custom packages, but I'm happy with that side. Main issue revolves around introduction of RPM4. Using 6.2 binary CD as base, genhdlist fails to deal with rpms >3.0. OK, recompiled genhdlist with later rpm libraries and -lpopt, & copied rpm binary across. (3.0.5). Seems to work OK until post-install, when discovered RPM4 rpms not installed (including kernel, etc). Trying upgrade from CD reports unresolved dependencies for those packages, but no suggestions, or further details. (am using updated boot disk and update disk) Attempted to duplicate RPM4 update to CD manually (db3, rpm, popt), but unfortunately this results in an early anaconda error referring to the infamous "undefined symbol:fdio". Can't find the rpm module to tell it about rpmio - suspect this is compiled in,. Try alternate approach - can I use RH7.1 install CD / floppy as a basis? (still want 6.2 installed). Replace all RPMs with the 6.2 set, and generate new hdlist (using recompiled 6.2 genhdlist, as no longer on 7.1 CD), and then a hdlist2 (with a dummy RPM), as it seems to insist on its presence. Current obstacle is in comps.py, in mergeFullHeaders: rpm.mergeHeaderListfromFD (self.hdlist,fd,1000004) rpm.error: match tag missing in new header Again, I can't find the rpm module, and can't work out why (or what) it is quizzing on the floppy (FD?). Does anyone have a clue on either approach? Or an alternate method that doesn't involve multiple CDs, and multiple manual selection of packages for update (rpm, etc, followed by others, with reboots inbetween - I can see stuff being missed, and inconsistent build states at the end of the process). I have, of course used the Burning a RedHat CD HOWTO, (v1.35), unfortunately it predates the RPM4 issue :-( All help, pointers, etc, gratefully received (I'll try to get any good stuff into the relevant docs) Regards, Mike Onyskiw
