public inbox for gentoo-server@lists.gentoo.org
 help / color / mirror / Atom feed
From: Karl Holz <karlg@rogers.com>
To: gentoo-server@lists.gentoo.org
Subject: Re: [gentoo-server] Best practices in managing large server groups
Date: Mon, 21 May 2007 11:10:37 -0400	[thread overview]
Message-ID: <246510DE-93FF-46CD-AF10-70C53C8442A7@rogers.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0705210945560.9909@office.4L>

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

On 21-May-07, at 5:04 AM, Ronan Mullally wrote:

> Does a multi-server gentoo install require a portage tree and gcc on
> each box?

No,  you can use the following command:

# ROOT="/chroot" emerge <pkages you want to install> -pv

this will allow you build a new system, and it wount install the gcc  
packages. all you'll need is a stage 3 tarball for building, edit  
the /etc/make.conf to what ever setting you desire. Just keep in mind  
you will need to install all the programs needed for boot: base- 
system, grep, openssh, pam, core-utills, etc.


> Is there a way to run gentoo without a portage tree on each box?

  yes, if  you setup a build system, using a stage3 tarball, and  
build your system into a directory. Portage will only be under your / 
usr/portage and not into the system image you're building. the good  
thing about using a Stage3 tarball is you can build you system on any  
linux system, build your system image, tarball the image, deploy and  
install grub on x86, yaboot on Mac PPC, silo on Sparc64.


__________________
Karl Gustav B. Holz
----------
karl@new-aeon.com
----------
http://www.new-aeon.com



[-- Attachment #2: Type: text/html, Size: 4030 bytes --]

  parent reply	other threads:[~2007-05-21 15:14 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-20 18:29 [gentoo-server] Best practices in managing large server groups Charles Duffy
2007-05-20 20:20 ` Nicolas MASSE
2007-05-20 20:34   ` Charles Duffy
2007-05-20 21:25 ` Ramon van Alteren
2007-05-21  9:04   ` Ronan Mullally
2007-05-21 13:44     ` Thilo Bangert
2007-05-21 14:30       ` Ronan Mullally
2007-05-21 14:36         ` Arturo 'Buanzo' Busleiman
2007-05-21 14:53           ` Ronan Mullally
2007-05-21 15:01             ` Arturo 'Buanzo' Busleiman
2007-05-21 15:28               ` Christian Bricart
2007-05-21 15:54                 ` Arturo 'Buanzo' Busleiman
2007-05-22  4:19             ` Justin Cataldo
2007-05-22  4:59             ` Brian Kroth
2007-05-21 15:10     ` Karl Holz [this message]
2007-05-21 15:51       ` Ronan Mullally
2007-05-21 16:27         ` Ryan Gibbons
2007-05-21 17:29           ` Ronan Mullally
2007-05-21 17:35             ` Petteri Räty
2007-05-21 17:46               ` Ronan Mullally
2007-05-21 17:47             ` José Costa
2007-05-21 17:54               ` José Costa
2007-05-21 22:58           ` Karl Holz
2007-05-21 23:11 ` Ramon van Alteren
2007-05-22  5:10   ` Brian Kroth
2007-05-22 16:54   ` Charles Duffy
2007-05-22 17:23     ` Wendall Cada
2007-05-22 21:06       ` [gentoo-server] " Charles Duffy
2007-05-23  1:33         ` Wendall Cada
2007-05-23  7:37     ` [gentoo-server] " Ramon van Alteren
2007-05-23 12:28       ` Andrew Gaffney
2007-05-23 13:03         ` Ramon van Alteren
2007-05-23 13:46           ` Andrew Gaffney
2007-05-26  9:53       ` Thilo Bangert
2007-05-22 12:58 ` Tomasz Szymczak

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=246510DE-93FF-46CD-AF10-70C53C8442A7@rogers.com \
    --to=karlg@rogers.com \
    --cc=gentoo-server@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