I've been over and over Tony's "Redhat 7 Customised Installer" HOWTO and Luigi's "Burning a RedHat CD HOWTO" documents and am still not sure I'm 'getting it' regarding the procedure to come up with a custom redhat-8.0 cdrom. When are the various steps required vs. when are they optional ? How do you know what's mandatory and what's optional ? Lets run through a few scenarios... Assume that the goal is to come up with a one-CD redhat-8.0 that will 'always' be installed via kickstart, sometime from local cdrom, sometime from local disk, and sometime using http. Is the following correct for redhat-8.0 ? My reading of the two docs above say that the basic procedure is: - copy redhat-8.0 cd-1 to disk - tweak the RedHat/RPMS tree to have just the rpms we need - run genhdlist against that tree to synch up its base/hdlist + hdlist2 files to the RPMS dir - don't worry with comps.xml since we didn't cause any new dependencies (stripping it down is optional ?) - don't bother running buildinstall, the package order didn't change - skip splitdistro and second genhdlist (it will fit on one cd) - run mkisofs and you're done Now consider modifying that cd to add all current updates - copy the built-above cd to disk - tweak the RedHat/RPMS tree to supersede the updated rpms - run genhdlist to update the mapping of package name to precise (updated) filename - skip changing comps.xml since no new dependencies were created - skip buildinstall since the package order didn't change - skip splitdistro and second genhdlist (it still fits on one cd) - run mkisofs and you're done Now add some custom rpms to that cd - copy the built-above cd including the updates - add the custom rpms to RedHat/RPMS - run genhdlist to update the mapping of package name to precise filename - do we need to add the new rpms to comps.xml if we always install via kickstart ? - do we need to run buildinstall at all ? - if it fits on one cd, skip splitdistro and second genhdlist ? - run mkisofs and you're done Lastly, suppose we want to precisely control the order our custom rpms installs in the kickstart process 'without' adding our rpms in %post in the ks.cfg file. Is that possible at all for a one-cd implementation ? The thing I'm struggling with is wording from Tony's HOWTO that says things like "...unless you want or need to rebuild the installer itself....", how do I know if I need to ? Any clarifications/corrections are appreciated.... -- ---------- Vince.Skahan@xxxxxxxxxx --------- Connexion by Boeing - Cabin Network
