public inbox for gentoo-catalyst@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] livecd-stage1 problem
Date: Thu, 13 Mar 2008 10:13:27 -0700	[thread overview]
Message-ID: <1205428407.7261.37.camel@inertia.twi-31o2.org> (raw)
In-Reply-To: <47D7F5E3.8060907@optaros.com>

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

On Wed, 2008-03-12 at 11:25 -0400, Robert C Corsaro wrote:
> What is the recommended way to learn to use catalyst?

# emerge catalyst
# mkdir -p /release
# cd /release
# svn co svn://svn.gentoo.org/releng
# cd releng/trunk/releases/2007.0/specs/amd64
# sed -i 's:/root/livecd/kconfig/2007.0/amd64:../../kconfig/amd64:' *.spec
# mkdir -p /var/tmp/catalyst/snapshots
# cd /var/tmp/catalyst/snapshots
# wget http://gentoo.osuosl.org/releases/snapshots/portage-2007.0.tar.bz2
# mkdir -p /var/tmp/catalyst/builds/default
# cd /var/tmp/catalyst/builds/default
# wget http://gentoo.osuosl.org/releases/amd64/2006.1/stages/stage3-amd64-2006.1.tar.bz2

Now, at this point, you'll have a proper checkout and be ready to go.  I
don't recommend using the 2008.0 specs until after they're finalized and
the release is made.

It's very simple.  Start with stage1, then stage2, then stage3, then
proceed on to your different CD media.  I'd suggest starting with
installcd-stage1, rather than livecd-stage1.  Make changes.  See what
those changes actually end up doing.  Read the specs
in /usr/share/doc/catalyst-*/examples...

-- 
Chris Gianelloni
Release Engineering Strategic Lead
Games Developer

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

  reply	other threads:[~2008-03-13 17:13 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-11 19:45 [gentoo-catalyst] livecd-stage1 problem Robert C Corsaro
2008-03-11 19:48 ` Andrew Gaffney
2008-03-11 19:51   ` Robert C Corsaro
2008-03-11 19:54     ` Andrew Gaffney
2008-03-12  4:33     ` Daniel Díaz
2008-03-13 17:00       ` Chris Gianelloni
2008-03-12 14:59 ` Chris Gianelloni
2008-03-12 15:14   ` Robert C Corsaro
2008-03-12 15:21     ` Andrew Gaffney
2008-03-12 15:25       ` Robert C Corsaro
2008-03-13 17:13         ` Chris Gianelloni [this message]
2008-03-13 17:03     ` Chris Gianelloni
2008-03-13 17:16       ` Robert C Corsaro
2008-03-13 17:22         ` Chris Gianelloni
2008-03-14  0:23           ` Daniel Díaz
2008-03-27  6:42             ` Chris Gianelloni
2008-04-04  2:43               ` Daniel Díaz

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=1205428407.7261.37.camel@inertia.twi-31o2.org \
    --to=wolf31o2@gentoo.org \
    --cc=gentoo-catalyst@lists.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