public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Nick Rout <nick@rout.co.nz>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Using Catalyst for an automated install.
Date: Wed, 19 May 2004 09:22:04 +1200	[thread overview]
Message-ID: <20040519092126.0FBC.NICK@rout.co.nz> (raw)
In-Reply-To: <1084883412.26952.28.camel@localhost>

Thanks chris, I'll file that away in the useful information section ;-)


On Tue, 18 May 2004 08:30:12 -0400
Chris Gianelloni <wolf31o2@gentoo.org> wrote:

> What you're looking for in catalyst is the runscript.  You will want to
> modify the runscript to do what you want.  In my case, I am building
> GameCDs, so I have copied the default-runscript.sh to
> gamecd-runscript.sh and have made my modifications there.  Then I simply
> put the path to gamecd-runscript.sh in my livecd-stage2.spec file and
> I'm done.
> 
> On Tue, 2004-05-18 at 00:10, Nick Rout wrote:
> > I have thought about this some more. how about 
> > 
> > 1. building a sample system with the packages and settings you want.
> > 
> > 2. create a backup with mondo-rescue
> > 
> > 3. boot the target machines with the mondo boot cd 
> > 
> > done.
> > 
> > On Mon, 17 May 2004 16:51:17 -0700
> > <ebrewer@cloudmark.com> wrote:
> > 


--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2004-05-18 21:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-17 23:51 [gentoo-dev] Using Catalyst for an automated install ebrewer
     [not found] ` <20040518160830.9998.NICK@rout.co.nz>
2004-05-18 12:30   ` Chris Gianelloni
2004-05-18 21:22     ` Nick Rout [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-05-18 17:10 ebrewer
2004-05-18 11:43 Josh Glover
2004-05-17 22:52 ebrewer
2004-05-17 23:33 ` Nick Rout
2004-05-17 23:50 ` John Davis

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=20040519092126.0FBC.NICK@rout.co.nz \
    --to=nick@rout.co.nz \
    --cc=gentoo-dev@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