This was discussed on this list before back in June and in relation to pungi 0.3.7 by Joel Andres Granados and others.
Using pungi I would like to create a CD that includes a kickstart file (ks.cfg) to be used during installation of a system using this CD.
Is there a way to tell pungi to put a ks.cfg file into the root of the CD? I am using pungi-1.1.5-1.fc8 on F8-test3.
What is the best way to modify the files in the isolinux directory? I.e. the file isolinux.cfg needs to be modified to use the ks.cfg file during boot. Should I create an RPM that overwrites these files already installed by the anaconda-runtime package or is there a more elegant way?
Without such a capability to add / modify key files pungi can only really be used to respin distributions, but not create installation CDs used for automated install or appliances. Is this maybe not the intention with this tool?
--martin
Martin Steinmann wrote:
This was discussed on this list before back in June and in relation to pungi 0.3.7 by Joel Andres Granados and others.
Using pungi I would like to create a CD that includes a kickstart file (ks.cfg) to be used during installation of a system using this CD.
Is there a way to tell pungi to put a ks.cfg file into the root of the CD? I am using pungi-1.1.5-1.fc8 on F8-test3.
What is the best way to modify the files in the isolinux directory? I.e. the file isolinux.cfg needs to be modified to use the ks.cfg file during boot. Should I create an RPM that overwrites these files already installed by the anaconda-runtime package or is there a more elegant way?
Without such a capability to add / modify key files pungi can only really be used to respin distributions, but not create installation CDs used for automated install or appliances. Is this maybe not the intention with this tool?
--martin
-- Fedora-buildsys-list mailing list Fedora-buildsys-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
It been a long time since I had a hard look at pungi. I do know that it went from config files to using kickstart. Maybe you can use the %post functionality of kickstart, not sure :(.
what version are you using? try using the latest version. http://hosted.fedoraproject.org/projects/pungi
Regards
On Tue, 16 Oct 2007 14:51:10 +0200 Joel Andres Granados jgranado@redhat.com wrote:
It been a long time since I had a hard look at pungi. I do know that it went from config files to using kickstart. Maybe you can use the %post functionality of kickstart, not sure :(.
what version are you using? try using the latest version. http://hosted.fedoraproject.org/projects/pungi
The %post part of a kickstart file is not yet processed by pungi. I haven't decided if or how it would be used.
Also there has been a slight regression in configurability in pungi with the move to using kickstart files. You can no longer override what "release note" files to lay onto the install tree. This was the method before to use to get files out of packages and place them on the tree/media. A file such as a kickstart file. Right now unfortunately you have to edit the source code itself, in pypungi/config.py. You can add another file regular expression to match your kickstart file, and list another package to the packages to look in for those files that has your kickstart file in it.
Jesse Keating wrote:
On Tue, 16 Oct 2007 14:51:10 +0200 Joel Andres Granados jgranado@redhat.com wrote:
It been a long time since I had a hard look at pungi. I do know that it went from config files to using kickstart. Maybe you can use the %post functionality of kickstart, not sure :(.
what version are you using? try using the latest version. http://hosted.fedoraproject.org/projects/pungi
The %post part of a kickstart file is not yet processed by pungi. I haven't decided if or how it would be used.
Also there has been a slight regression in configurability in pungi with the move to using kickstart files. You can no longer override what "release note" files to lay onto the install tree. This was the method before to use to get files out of packages and place them on the tree/media. A file such as a kickstart file. Right now unfortunately you have to edit the source code itself, in pypungi/config.py. You can add another file regular expression to match your kickstart file, and list another package to the packages to look in for those files that has your kickstart file in it.
-- Fedora-buildsys-list mailing list Fedora-buildsys-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
I think you can also add the file to the resulting iso image. it should be easier than changing the code (IMO) 1. you have to mount the iso image somewhere `mount -o loop /path/to/isoimage /mount/dir` 2. cp -rf /mount/dir /other/temp/dir 3. cp kickstart.cfg /other/temp/dir 4. umount /mount/dir 5. mkisofs ... 6. put iso on cd
I'm not really sure how the mkisofs command goes. but you can always look at the pungi code and see what is done there :)
Be sure that the copy takes two hidden files that are at the root.
I think you can also add the file to the resulting iso image. it should be easier than changing the code (IMO)
- you have to mount the iso image somewhere `mount -o loop
/path/to/isoimage /mount/dir` 2. cp -rf /mount/dir /other/temp/dir 3. cp kickstart.cfg /other/temp/dir 4. umount /mount/dir 5. mkisofs ... 6. put iso on cd
I'm not really sure how the mkisofs command goes. but you can always
look >at the pungi
code and see what is done there :)
Be sure that the copy takes two hidden files that are at the root.
Joel
Many thanks for all the great suggestions - very helpful.
We actually have a fully automated build system that creates CDs currently for RHEL4, RHEL5 and FC6. This is done by reverse engineering starting with disk 1 of the official distribution. We then create a new custom CD with a new repository, new metadata and we have to open and change the stage2 image as well to change the look & feel during installation. This is messy as you can imagine, but it works.
For F7 we were hoping we could use pungi, but the pungi development now moved on to F8. Therefore, I don't think we will do an F7 based appliance.
On F8 we were hoping pungi could do what we needed - pretty basic stuff after all as most of it can be added as RPMs (except kickstart files and modifications to files in the isolinux directory). I am not so keen changing the pungi code as pungi is still under heavy development and will therefore likely change. Therefore, we might choose your proposed approach of modifying the CD that was created with pungi in the first place. Still messy but slightly better than before.
Eventually we hope that there will be a tool to create appliances. After all, just re-spinning Fedora or RHEL distributions is only fun the first time, but provides little value unless it can be turned either into an automated install or an appliance with custom look & feel, or both.
BTW: The project I am working on is at http://www.sipfoundry.org
--martin
Martin Steinmann wrote:
I think you can also add the file to the resulting iso image. it should be easier than changing the code (IMO)
- you have to mount the iso image somewhere `mount -o loop
/path/to/isoimage /mount/dir` 2. cp -rf /mount/dir /other/temp/dir 3. cp kickstart.cfg /other/temp/dir 4. umount /mount/dir 5. mkisofs ... 6. put iso on cd
I'm not really sure how the mkisofs command goes. but you can always
look >at the pungi
code and see what is done there :)
Be sure that the copy takes two hidden files that are at the root.
Joel
Many thanks for all the great suggestions - very helpful.
We actually have a fully automated build system that creates CDs currently for RHEL4, RHEL5 and FC6. This is done by reverse engineering starting with disk 1 of the official distribution. We then create a new custom CD with a new repository, new metadata and we have to open and change the stage2 image as well to change the look & feel during installation. This is messy as you can imagine, but it works.
For F7 we were hoping we could use pungi, but the pungi development now moved on to F8. Therefore, I don't think we will do an F7 based appliance.
On F8 we were hoping pungi could do what we needed - pretty basic stuff after all as most of it can be added as RPMs (except kickstart files and modifications to files in the isolinux directory). I am not so keen changing the pungi code as pungi is still under heavy development and will therefore likely change. Therefore, we might choose your proposed approach of modifying the CD that was created with pungi in the first place. Still messy but slightly better than before.
Eventually we hope that there will be a tool to create appliances. After all, just re-spinning Fedora or RHEL distributions is only fun the first time, but provides little value unless it can be turned either into an automated install or an appliance with custom look & feel, or both.
BTW: The project I am working on is at http://www.sipfoundry.org
--martin
-- Fedora-buildsys-list mailing list Fedora-buildsys-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
There is also the fedora livecd to play with. You can basically put together a bunch of apps and configure them in a certain way. When the livecd is created, you can boot it in pretty much any computer to show off your stuff. There is also revisor that tries to put pungi and livecd together into a very user friendly interface. It also has more funtionalities that I don't know about :(
hope it helps.
buildsys@lists.fedoraproject.org
-
Jesse Keating -
Joel Andres Granados -
Martin Steinmann