From: Lars Weiler <pylon@gentoo.org>
To: ppc@gentoo.org, ppc64@gentoo.org
Cc: gentoo-releng@lists.gentoo.org
Subject: [gentoo-releng] ppc outlines for the release
Date: Wed, 6 Jul 2005 00:45:42 +0200 [thread overview]
Message-ID: <20050705224542.GI31682@celeborn.wh-og.hs-niederrhein.de> (raw)
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
next reply other threads:[~2005-07-05 22:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-05 22:45 Lars Weiler [this message]
2005-07-06 6:19 ` [gentoo-releng] Re: ppc outlines for the release Daniel Ostrow
2005-07-06 7:17 ` Lars Weiler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050705224542.GI31682@celeborn.wh-og.hs-niederrhein.de \
--to=pylon@gentoo.org \
--cc=gentoo-releng@lists.gentoo.org \
--cc=ppc64@gentoo.org \
--cc=ppc@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox