From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.62) (envelope-from ) id 1HqACu-0006rG-LT for garchives@archives.gentoo.org; Mon, 21 May 2007 15:54:01 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.14.0/8.14.0) with SMTP id l4LFrQjA013422; Mon, 21 May 2007 15:53:27 GMT Received: from mail.4L.ie (mail.4L.ie [193.27.1.25]) by robin.gentoo.org (8.14.0/8.14.0) with ESMTP id l4LFpUGd011097 for ; Mon, 21 May 2007 15:51:30 GMT Received: from oook.4L.ie (host86-140-171-94.range86-140.btcentralplus.com [86.140.171.94]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "oook.4L.ie", Issuer "CA Cert Signing Authority" (verified OK)) by mail.4L.ie (Postfix) with ESMTP id B888E17828 for ; Mon, 21 May 2007 16:51:29 +0100 (BST) Received: from office.4L (office.4L [192.168.1.106]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by oook.4L.ie (Postfix) with ESMTP id AD6D22F4E for ; Mon, 21 May 2007 16:51:28 +0100 (BST) Date: Mon, 21 May 2007 16:51:28 +0100 (BST) From: Ronan Mullally X-X-Sender: ronan@office.4L To: gentoo-server@lists.gentoo.org Subject: Re: [gentoo-server] Best practices in managing large server groups In-Reply-To: <246510DE-93FF-46CD-AF10-70C53C8442A7@rogers.com> Message-ID: References: <4650937E.80301@spamcop.net> <4650BCC7.60909@vanalteren.nl> <246510DE-93FF-46CD-AF10-70C53C8442A7@rogers.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-server@gentoo.org Reply-to: gentoo-server@lists.gentoo.org MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Archives-Salt: d599c8e9-2d68-4590-bf5e-77065dc0fb86 X-Archives-Hash: 8e4f85e2769ec1990cecebe87ff63eed Hi Karl, On Mon, 21 May 2007, Karl Holz wrote: > >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. How are updates handled? "emerge -uD " isn't going to work without a portage tree, so I presume I'd need to tell each server which packages need to be updated with "emerge ... " to have it download them from the binhost? -Ronan -- gentoo-server@gentoo.org mailing list