Pungi / anaconda: seeding the pkg selection
 

The installer cd I'm trying to build (for the School Server) is driven
by 2 custom packages - a metapackage that pulls in all the
dependenciess, and a configuration package that whacks /etc .

Feeding those to Pungi via a kickstart file gets them on the installer
CD, but does not get them installed by default. My overall goals (and
stumbling blocks) are:

1 - Support interactive installs (that defaults to installing the XS
packages!) for developers & pilot sites. This should be the default on
the grub menu...

- How do get anaconda to pick those 2 custom packages by default?
Using a kickstart file is not an option - it switches off the
interactive install mode. Is anaconda auto-installing the 'base' group
and should I add them there? Should I create a new group in comps.xml
and get anaconda to have it selected by default?

- How can I feed Pungi a custom comps.xml?

1.1 - The interactive install should have a custom 'default' layout
for the autopartitioning. Can I seed that somehow?

2 - Support a fully automated kickstart install (non-default option
in grub menu). This is also an example for local teams to edit to
their needs...

- Does Pungi support a %post that can "copy in" a new grub menu to
the isolinux/syslinux directory?

- ... and add a ks.cfg file to the initrd?

- Will anaconda probe for ks.cfg in any directories that are easier
to edit than the initrd?

lots of questions :-/

cheers,



m
--
martin.langhoff@gmail.com
martin@laptop.org -- School Server Architect
- ask interesting questions
- don't get distracted with shiny stuff - working code first
- http://wiki.laptop.org/go/User:Martinlanghoff

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

Pungi / anaconda: seeding the pkg selection
 

On Wed, 2008-09-03 at 18:46 +1200, Martin Langhoff wrote:
> The installer cd I'm trying to build (for the School Server) is driven
> by 2 custom packages - a metapackage that pulls in all the
> dependenciess, and a configuration package that whacks /etc .
>
> Feeding those to Pungi via a kickstart file gets them on the installer
> CD, but does not get them installed by default. My overall goals (and
> stumbling blocks) are:
>
> 1 - Support interactive installs (that defaults to installing the XS
> packages!) for developers & pilot sites. This should be the default on
> the grub menu...
>
> - How do get anaconda to pick those 2 custom packages by default?
> Using a kickstart file is not an option - it switches off the
> interactive install mode.

why not a kickstart with 'interactive' in the file:

http://www.redhat.com/docs/manuals/enterprise/RHEL-5-manual/Installation_Guide-en-US/s1-kickstart2-options.html

Pretty sure it's in F9, too - I just found the rhel5 ks manual faster.

-sv


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

Pungi / anaconda: seeding the pkg selection
 

On Wed, Sep 3, 2008 at 7:03 PM, Seth Vidal <skvidal@fedoraproject.org> wrote:
> why not a kickstart with 'interactive' in the file:
> http://www.redhat.com/docs/manuals/enterprise/RHEL-5-manual/Installation_Guide-en-US/s1-kickstart2-options.html

Bah, too easy to be true -- ;-) Thanks a lot for the hint - I'll try
it. Wonder whether it also does the "load defaults but work
interactively" trick with the disk partitioner.



cheers,



m
--
martin.langhoff@gmail.com
martin@laptop.org -- School Server Architect
- ask interesting questions
- don't get distracted with shiny stuff - working code first
- http://wiki.laptop.org/go/User:Martinlanghoff

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

Pungi / anaconda: seeding the pkg selection
 

Martin Langhoff wrote:

On Wed, Sep 3, 2008 at 7:03 PM, Seth Vidal <skvidal@fedoraproject.org> wrote:

why not a kickstart with 'interactive' in the file:
http://www.redhat.com/docs/manuals/enterprise/RHEL-5-manual/Installation_Guide-en-US/s1-kickstart2-options.html


Bah, too easy to be true -- ;-) Thanks a lot for the hint - I'll try
it. Wonder whether it also does the "load defaults but work
interactively" trick with the disk partitioner.



IIRC, yes it does.

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

Pungi / anaconda: seeding the pkg selection
 

On Wed, Sep 3, 2008 at 6:46 PM, Martin Langhoff > 1.1 - The
interactive install should have a custom 'default' layout
> for the autopartitioning. Can I seed that somehow?
>
> 2 - Support a fully automated kickstart install (non-default option
> in grub menu). This is also an example for local teams to edit to
> their needs...
>
> - Does Pungi support a %post that can "copy in" a new grub menu to
> the isolinux/syslinux directory?
> - ... and add a ks.cfg file to the initrd?

So I guess this is the question that remains - how to feed a ks file
to Pungi. Google only finds discussions about the F7 Pungi (which
could not do it), and in looking at the src I can't see any references
to %post.

cheers,



m
--
martin.langhoff@gmail.com
martin@laptop.org -- School Server Architect
- ask interesting questions
- don't get distracted with shiny stuff - working code first
- http://wiki.laptop.org/go/User:Martinlanghoff

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