pungi used to create CD that includes a kickstart file

Jeffrey C. Ollie jeff at ocjtech.us
Thu Jun 14 12:49:54 UTC 2007


On Thu, 2007-06-14 at 07:22 -0400, Jesse Keating wrote:
> On Thursday 14 June 2007 07:20:54 Jeroen van Meeuwen wrote:
> > One example that comes to mind is a respin for different branch offices,
> > having different kickstart files, although someone doing different
> > kickstart files for different branch offices should be able to package
> > it up.
> >
> > Another reason is that one may want to copy a tree (or files within that
> > tree) from the install media to the installed system, like configuration
> > files, home directories, etc.
> >
> > Another reason is that Revisor doesn't package things up.
> 
> I see nothing in these reasons that prevents a package of the files from being 
> created.
> 
> I'm not saying no to the feature yet, I just need to think about it a bit and 
> what it means to pungi.

If you wanted to include some custom kickstart files on the CD so that
you could do something like:

linux ks=cdrom:/kickstart/officeworker.cfg

or:

linux ks=cdrom:/kickstart/webfarmserver.cfg

In cases like this, the files can't be packaged up in some RPM.  I'm
sure that having unpacked files on the CD could be useful for some %pre
and %post scripts as well.

Jeff

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://listman.redhat.com/archives/fedora-buildsys-list/attachments/20070614/069e89db/attachment.sig>


More information about the Fedora-buildsys-list mailing list