On Thursday 14 June 2007 09:57:38 Martin Steinmann wrote: > - Find the RPM package that provides isolinux.cfg (I haven't found it yet) > - Patch the source and create a new custom package > - Substitute the original package with the new one in the comps file, so > that the original one does not get loaded as a mandatory package - Maintain > that custom package going forward (It needs a different name so that yum > update does not load the original one back, but that could mess up other > packages that depend on it - don't know yet) > > The alternative seems much easier: Copy the altered isolinux.cfg file into > the tree after buildinstall. Although I do agree that packaging all this is > the cleaner approach. > > To create an appliance pungi needs to offer the ability to customize the > stage 1 installation process. The stage 2 installation process can then be > customized using a regular kickstart file. Althoigh I haven't yet gotten to > customizing the stage2 graphics and might run into other issues there.
When you're to this point, you probably just want to modify anaconda directly. Anaconda(-runtime) is what writes out the isolinux config files. You're going to be modifying a bunch of other stuff if you're going to be producing an appliance, trademark and copyright usage and all that jazz. -- Jesse Keating Release Engineer: Fedora
pgpW1QHqKNRCi.pgp
Description: PGP signature
-- Fedora-buildsys-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
