pungi used to create CD that includes a kickstart file [PATCH]
jkeating at redhat.com
Thu Jun 14 14:31:35 UTC 2007
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.
Release Engineer: Fedora
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: not available
Url : http://lists.fedoraproject.org/pipermail/buildsys/attachments/20070614/cb93ee2d/attachment.bin
More information about the buildsys