public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Duncan" <1i5t5.duncan@cox.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64]  Re: new graphical installer
Date: Fri, 11 Aug 2006 22:26:40 +0000 (UTC)	[thread overview]
Message-ID: <ebj06v$tve$4@sea.gmane.org> (raw)
In-Reply-To: 200608111307.46197.tcoulon@decoulon.ch

Thierry de Coulon <tcoulon@decoulon.ch> posted
200608111307.46197.tcoulon@decoulon.ch, excerpted below, on  Fri, 11 Aug
2006 13:07:46 +0200:

> Anyway, you have to download the iso file to be able tu burn it to CD.
> I'm not aware of any way of installing Gentoo on many pc's without
> either compiling it pc after pc, or possibly creating an image of the
> first install and copying it (provided all pcs are the same, of course).

Note portage FEATURES=buildpkg, one of my favorite features, for a number
of reasons.  Once you have the first one setup, all others can install
using the binary packages created by the first one.  Thus, the process
becomes much like installing a regular binary distribution, only of course
with Gentoo details, and using the binary packages (emerge -K) created for
the first one.

Also note that with a group of computers, it's possible to use distcc to
share in the compiling job, once they all get minimally setup, anyway. 
Thus, I'd setup the first one thru the emerge --emptytree system step (or
maybe even before that, with just the stage-3 and networking stuff), ensure
it's configured for networking, then setup the others to the same level,
and get distcc merged on all of them. After that, you can use distcc to
while compiling everything else, and the job will go far faster.

Of course, that assumes that you want to use the same USE flags and CFLAGS
on all of them.  If not, you can't share packages, but you can still use
distcc to share the compiling.

For big installs, you can use dev-util/catalyst, the Gentoo release creator
meta-tool that releng uses for Gentoo's own releases, and customize the
install as desired for your own purposes.  Obviously, it'll be more work
to figure that out and use it if you are only doing a few installs, but
once you get into the double-digits, it could be easier using catalyst to
customize your own install, and time you reach fifty, catalyst should save
you some major time and hassle, repeatedly configuring the same thing
fifty times.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-amd64@gentoo.org mailing list



      reply	other threads:[~2006-08-11 22:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-11 11:15 [gentoo-amd64] new graphical installer Gavin Seddon
2006-08-11 11:07 ` Thierry de Coulon
2006-08-11 22:26   ` Duncan [this message]

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='ebj06v$tve$4@sea.gmane.org' \
    --to=1i5t5.duncan@cox.net \
    --cc=gentoo-amd64@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