FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Fedora Build System

 
 
LinkBack Thread Tools
 
Old 11-21-2007, 09:40 AM
Peter Åstrand
 
Default A few Pungi questions

Hi, I have a few questions about Pungi:

* When running the text based Anaconda from the resulting ISO, all
packages are selectable, not just those that are included in the custom
dist. Is this a known limitation? Any other problems with the text based
Anaconda, to watch out for?


* How can I create a CD that automatically uses a kickstart file? Revisor
seems to support this, but we're using Pungi. I've found
http://www.redhat.com/archives/fedora-buildsys-list/2007-June/msg00098.html,
but perhaps there's a better way to do this?


* Where can I find documentation on the "special" Kickstart options that
Pungi understands, are there any others than "repo"?

I also wonder if anyone has a minimal KS (but with X11) file to be used as
a template.


Best regards,
---
Peter Åstrand ThinLinc Chief Developer
Cendio AB http://www.cendio.se
Wallenbergs gata 4
583 30 Linköping Phone: +46-13-21 46 00--
Fedora-buildsys-list mailing list
Fedora-buildsys-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
 
Old 11-21-2007, 09:55 AM
Jeroen van Meeuwen
 
Default A few Pungi questions

Peter Åstrand wrote:

Hi, I have a few questions about Pungi:

* When running the text based Anaconda from the resulting ISO, all
packages are selectable, not just those that are included in the custom
dist. Is this a known limitation? Any other problems with the text based
Anaconda, to watch out for?




As far as I can see, anaconda uses comps to determine what groups to
display. If you have some third party packages, create a third party
repository with a comps.xml and pungi should write out a merged comps file.




* How can I create a CD that automatically uses a kickstart file? Revisor
seems to support this, but we're using Pungi. I've found
http://www.redhat.com/archives/fedora-buildsys-list/2007-June/msg00098.html,
but perhaps there's a better way to do this?




Using pungi's different 'stages' that you can enable and disable, first
compose a 'tree' -but not yet build an ISO, then copy in to that tree
your ks.cfg and modify isolinux/isolinux.cfg to 'append ks'. Then run
the final pungi stages.




* Where can I find documentation on the "special" Kickstart options that
Pungi understands, are there any others than "repo"?


I also wonder if anyone has a minimal KS (but with X11) file to be used as
a template.




A minimal ks with X11 seems to me like you need:

%packages --nobase
@base-x
%end

It'll pull in dependencies for @base-x, but not add the @core group.

Kind regards,

Jeroen van Meeuwen
-kanarip

--
Fedora-buildsys-list mailing list
Fedora-buildsys-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
 
Old 11-21-2007, 12:26 PM
Jesse Keating
 
Default A few Pungi questions

On Wed, 21 Nov 2007 11:40:15 +0100 (CET)
Peter Åstrand <astrand@cendio.se> wrote:

> * Where can I find documentation on the "special" Kickstart options
> that Pungi understands, are there any others than "repo"?

Jeroen answered the other questions for me.

"repo" isn't a "special" kickstart option. It's used by anaconda to
access additional repositories during install. The only "special"
thing that pungi uses is a partition type of "iso" to indicate how
large you want your isos to be.

--
Jesse Keating
Fedora -- All my bits are free, are yours?
--
Fedora-buildsys-list mailing list
Fedora-buildsys-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
 
Old 11-21-2007, 12:47 PM
Peter Åstrand
 
Default A few Pungi questions

> > * When running the text based Anaconda from the resulting ISO, all
> > packages are selectable, not just those that are included in the custom
> > dist. Is this a known limitation? Any other problems with the text based
> > Anaconda, to watch out for?
> >
>
> As far as I can see, anaconda uses comps to determine what groups to display.
> If you have some third party packages, create a third party repository with a
> comps.xml and pungi should write out a merged comps file.

I've verified that a comps file is indeed created
(DESTDIR/VERSION/i386/os/repodata/NAME-VERSION-comps.xml), but it contains
all packages, for example scribus, even though this RPM is not included.

Somehow, the GUI Anaconda seems to "hide" the packages that are not
available, while the text based Anaconda doesn't.


> > * How can I create a CD that automatically uses a kickstart file? Revisor
> > seems to support this, but we're using Pungi. I've found
> > http://www.redhat.com/archives/fedora-buildsys-list/2007-June/msg00098.html,
> > but perhaps there's a better way to do this?
> >
>
> Using pungi's different 'stages' that you can enable and disable, first
> compose a 'tree' -but not yet build an ISO, then copy in to that tree your
> ks.cfg and modify isolinux/isolinux.cfg to 'append ks'. Then run the final
> pungi stages.

Thanks. I wonder if this is the approach Revisor uses?


> > I also wonder if anyone has a minimal KS (but with X11) file to be used as a
> > template.
> >
>
> A minimal ks with X11 seems to me like you need:
>
> %packages --nobase
> @base-x
> %end

It seems anaconda-runtime is required as well.

Also, the resulting installer crashes when trying to install the
bootloader. I guess I need to add Grub as well.

Rgds,
---
Peter Åstrand ThinLinc Chief Developer
Cendio AB http://www.cendio.se
Wallenbergs gata 4
583 30 Linköping Phone: +46-13-21 46 00--
Fedora-buildsys-list mailing list
Fedora-buildsys-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
 
Old 11-21-2007, 01:11 PM
Jesse Keating
 
Default A few Pungi questions

On Wed, 21 Nov 2007 14:47:14 +0100 (CET)
Peter Åstrand <astrand@cendio.se> wrote:

> I've verified that a comps file is indeed created
> (DESTDIR/VERSION/i386/os/repodata/NAME-VERSION-comps.xml), but it
> contains all packages, for example scribus, even though this RPM is
> not included.
>
> Somehow, the GUI Anaconda seems to "hide" the packages that are not
> available, while the text based Anaconda doesn't.

Hrm, sounds like maybe a bug in the Anaconda text mode.


> > %packages --nobase
> > @base-x
> > %end
>
> It seems anaconda-runtime is required as well.
>
> Also, the resulting installer crashes when trying to install the
> bootloader. I guess I need to add Grub as well.

Yeah, I haven't yet hardcoded a list of absolutely needed for compose
packages.

# Compose Needs
anaconda-runtime
iscsi-initiator-utils
memtest86+
vnc-server

is what I have listed in the config that made F8. Of course, I'm
relying upon grub coming in from core group, and a few other things
from other groups.

--
Jesse Keating
Fedora -- All my bits are free, are yours?
--
Fedora-buildsys-list mailing list
Fedora-buildsys-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
 
Old 11-21-2007, 02:06 PM
Jeroen van Meeuwen
 
Default A few Pungi questions

Peter Åstrand wrote:
* When running the text based Anaconda from the resulting ISO, all
packages are selectable, not just those that are included in the custom

dist. Is this a known limitation? Any other problems with the text based
Anaconda, to watch out for?


As far as I can see, anaconda uses comps to determine what groups to display.
If you have some third party packages, create a third party repository with a
comps.xml and pungi should write out a merged comps file.


I've verified that a comps file is indeed created
(DESTDIR/VERSION/i386/os/repodata/NAME-VERSION-comps.xml), but it contains
all packages, for example scribus, even though this RPM is not included.

Somehow, the GUI Anaconda seems to "hide" the packages that are not
available, while the text based Anaconda doesn't.



That could very well be true; I haven't looked at how anaconda does the
text interface all too well.




* How can I create a CD that automatically uses a kickstart file? Revisor
seems to support this, but we're using Pungi. I've found

http://www.redhat.com/archives/fedora-buildsys-list/2007-June/msg00098.html,
but perhaps there's a better way to do this?


Using pungi's different 'stages' that you can enable and disable, first
compose a 'tree' -but not yet build an ISO, then copy in to that tree your
ks.cfg and modify isolinux/isolinux.cfg to 'append ks'. Then run the final
pungi stages.


Thanks. I wonder if this is the approach Revisor uses?



Revisor doesn't have these stages you can run separately, although
Revisor development is on it's way to fully enable modules to hook into
different stages of the process.


Anyway what Revisor does is compose a tree, then inserts the kickstart
file as /ks.cfg and modifies isolinux.cfg appending a "Install with
kickstart" bootloader menu option. So, similar to what you would do with
pungi but without the stages and manual changes.





I also wonder if anyone has a minimal KS (but with X11) file to be used as a
template.


A minimal ks with X11 seems to me like you need:

%packages --nobase
@base-x
%end


It seems anaconda-runtime is required as well.

Also, the resulting installer crashes when trying to install the
bootloader. I guess I need to add Grub as well.



Hmm, yes. I forgot; Revisor forcibly adds these required packages
-regardless of whether you've selected them or not-, unless you override
the variable in the configuration files.


Kind regards,

Jeroen van Meeuwen
-kanarip

--
Fedora-buildsys-list mailing list
Fedora-buildsys-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
 

Thread Tools




All times are GMT. The time now is 05:49 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright ©2007 - 2008, www.linux-archive.org