Could anyone get me some docs on how catalyst functions wrt. livecd
creation? I'm interested in the following aspects:
- How do catalyst and genkernel interact?
- What exactly do the different livecd stages do?
- Is it possible to specify on a per-arch basis what gets zapmosted
(thinking in terms of both the current ppc and old x86 scripts)? For
instance, what happens to non-x86 keymaps on a ppc livecd.
- How do I create the actual livecd? Is there some kind of scripting
that puts grp, stages, sources, initrd, kernel, bootloader, ... all on
the disc the livecd tool should produce?
I heard x86 was going to consider a one disc release containing both
some GRP and a working X for fosdem. Is this the new official format?
Am I allowed to use catalyst only for grp and stages for a fosdem
release and use my current livecd script to create the actual discs?
Is it possible to get an update on catalyst and genkernel progress in
general? Is there a possibility ppc64 could integrate ppc32 livecd
support into catalyst? If I'm not mistaken brad_mssw is closely related
to both ppc64, catalyst, genkernel and even amd64 for which already
livecds have been created using catalyst. I guess this would speed up
development enourmeously. This brings me to another question:
Is it possible for releng to be more verbose regarding what the
developers they gave access to their infrastructure for powerpc work
are actually working on? Wouldn't it be a good idea to create some
guidelines or policies about interaction between projects? I think some
current ppc subprojects (such as the QA projects) have guidelines about
things like masking packages stable, I think those need to be
communicated in an effective way to the developers now doing powerpc
work. While I was looking at catalyst I detected some packages which
were marked stable on ppc, but will never work on ppc (bootsplash was
one of them: ofb does not allow bootsplash to be used afaik.).
email@example.com mailing list