[gentoo-releng] ppc outlines for the release

[gentoo-releng] ppc outlines for the release

[Lars Weiler]

Hi all,

I had a talk about the release with corsair last Friday and
tried to point out some things for ppc32 and ppc64.

Although ppc64 is able to use multilib, we would do separate
releases.  Well, we could include two squashfs on the LiveCD
and boot separate kernels, but that will only stress our
mirrors as every ppc-user has to download stuff he (mostly)
does not need.

ppc32 prerelease LiveCDs will be ready soon (I just need to
run livecd-stage2 when I get genkernel to work properly ;)).
If it's possible we would like to mirror them like x86 and
let some users with brand-new Apple-hardware test them.  Our
kernel will be 2.6.12 (I use that snapshot), as this one
gives much more support for new Apples.  I will include two
or three kernels on the LiveCD: common Apple, Pegasos and
probably RS/6000.  Still we need a confirmation if initramfs
works on Pegasos (I guess not, or only with the patch
plasmaroo had to create for the Itaniums).

ppc32 is missing a 2005.1-profile!  This is urgent and must
be done soon, so that I can test it.  Changes would be to
create profiles for G3, G4, Pegasos, rs6k and OldWorld.
Mostly some USE-Flags must be set or another default
bootloader.

ppc64 has a nice new profile, but it seems that there are
some hickups ;-)

We want to cut the support of too many stages and GRP-sets.
My aim is:
* ppc32-generic (ppc60x, G3/ppc75x)
* ppc32-altivec (G4/ppc74xx)
* ppc64

That means stripping G3 and G5 ppc32 stages and GRP.  The
difference between ppc-generic and G3 is too small that we
need separate stages for it.  The main-difference on ppc32
is altivec-enabled/-disabled what gives enormous performance
boosts.  G5-ppc32-stages will also vanish, as ppc64 is able
to provide multilib-support, running 32/64-bit-userland with
a 64-bit-kernel, like on amd64.  And so a 32-bit-only system
makes no sense.


My personal problem is that I had to switch from the Pegasos
to a PowerMac 533 as my release-build-machine.  But somehow
that machine is not much slower than the Pegasos, so that I
think I can create the stages and LiveCD on my own (needs
about 14 hours for stage1-3).  But I really need help in the
GRP-bulding.  If we want to provide kde-meta, the machine
will need more than three days for a complete GRP build...
But I already talked to corsair that I may get an account on
his Dual-G5 and can build the stages in a chroot.  Or I'll
come over to him for a cup of coffee (hey, he lives in my
10km-bicycle-radius! :-) ), while the GRP-set builds.

So far the status of ppc-release-building.  If you have any
comments (I hope, I told everything correct about ppc64),
just reply to this message or reach me on IRC (when I'm
online ;) ).

Regards, Lars

-- 
Lars Weiler  <pylon@gentoo.org>  +49-171-1963258
Gentoo Linux PowerPC    : Developer and Release Engineer
Gentoo Infrastructure   : CVS Administrator
Gentoo Foundation       : Trustee
-- 
gentoo-releng@gentoo.org mailing list

[gentoo-releng] Re: ppc outlines for the release

[Daniel Ostrow]

[-- Attachment #1: Type: text/plain, Size: 1901 bytes --]

<snip>

> Although ppc64 is able to use multilib, we would do separate
> releases.  Well, we could include two squashfs on the LiveCD
> and boot separate kernels, but that will only stress our
> mirrors as every ppc-user has to download stuff he (mostly)
> does not need.

Agreed. ppc and ppc64 will have separate livecds for this release.

<snip>

> ppc32 is missing a 2005.1-profile!  This is urgent and must
> be done soon, so that I can test it.  Changes would be to
> create profiles for G3, G4, Pegasos, rs6k and OldWorld.
> Mostly some USE-Flags must be set or another default
> bootloader.
> 
> ppc64 has a nice new profile, but it seems that there are
> some hickups ;-)

The new profiles are in and all under
default-linux/ppc/2005.1/{ppc,ppc64}. Check them out while they are
still hot.

> We want to cut the support of too many stages and GRP-sets.
> My aim is:
> * ppc32-generic (ppc60x, G3/ppc75x)
> * ppc32-altivec (G4/ppc74xx)
> * ppc64

Speaking only for ppc64, we have MANY potential targets and have yet to
finalize a decision on what we will be providing stages for, what will
be going on the main mirrors and what will be hitting bit-torrent. The
multilib targets are still a bit too fresh in my opinion to be
considering making something as popular as the G5 stages multilib only,
chances are that there will be both 32 and 64-bit userland releases.
Multilib stuff is probably going to be bit-torrent only, or maybe just a
stage1 that users can build off of. There are a lot of choices out there
and I'm trying to be conscious of our mirror space.

Regarding ppc32 I see the following as a good target:

Generic ppc32 stage1
Generic ppc32 stage2
G4 stage2
Generic ppc32 stage3
G4 stage3
Pegasos stage3

This leaves users the ability to create a G3 optimized system off of the
Generic stage{1,2}. 

<snip>

Thanks,

--Dan

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-releng] Re: ppc outlines for the release

[Lars Weiler]

[-- Attachment #1: Type: text/plain, Size: 1036 bytes --]

* Daniel Ostrow <dostrow@gentoo.org> [05/07/06 02:19 -0400]:
> The new profiles are in and all under
> default-linux/ppc/2005.1/{ppc,ppc64}. Check them out while they are
> still hot.

Cool, thanks!

[...]
> considering making something as popular as the G5 stages multilib only,
> chances are that there will be both 32 and 64-bit userland releases.

Good.  That means I don't need a G5-32bit-Kernel, as this
processor will be provided by the ppc64-team completely.

> Regarding ppc32 I see the following as a good target:
> 
> Generic ppc32 stage1
> Generic ppc32 stage2
> G4 stage2
> Generic ppc32 stage3
> G4 stage3
> Pegasos stage3

I'm fine with that.  Pegasos has only changes in the virtual
and packages.  That means, it is usually the same like G4,
but without some Applec-specific stuff.

Regards, Lars

-- 
Lars Weiler  <pylon@gentoo.org>  +49-171-1963258
Gentoo Linux PowerPC    : Developer and Release Engineer
Gentoo Infrastructure   : CVS Administrator
Gentoo Foundation       : Trustee

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]