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 1HqC2N-0005HH-6S for garchives@archives.gentoo.org; Mon, 21 May 2007 17:51:15 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.14.0/8.14.0) with SMTP id l4LHoeGH023507; Mon, 21 May 2007 17:50:40 GMT Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.226]) by robin.gentoo.org (8.14.0/8.14.0) with ESMTP id l4LHllFF019679 for ; Mon, 21 May 2007 17:47:47 GMT Received: by nz-out-0506.google.com with SMTP id x7so2035929nzc for ; Mon, 21 May 2007 10:47:46 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=JZpQKOaMx18plJIn3hMCW14qoYz3y01KouK1tVFnq2/8ITDmSg0rCXn6IwTdCE2IEBC6hjYFXN6FDCYguAw/NlwXj7BddZ/c6WHeRouf+LRzWIMJtVwibUFs6Ny+NPxYyotbPoykYqrIFDeOg5Jsgie4rdXiUYfF2WzwoxFQ1i0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=AmclQxEqZfp8G5IL5pOy1g2/dXLsF+cT0BS43dR6ukHEbzSRVjywm8ARhI9ohR9foa2r9TboGjEK9oC2dsG7oneU4iUzK1edlwaVVnCpPAXM895vABGjS49E7y2i9SO3KtIgnQiq5Sx1T6r+rwqhqzLcnC3ZyCmkZeIy8VJNQs8= Received: by 10.114.88.1 with SMTP id l1mr2809526wab.1179769666349; Mon, 21 May 2007 10:47:46 -0700 (PDT) Received: by 10.115.111.5 with HTTP; Mon, 21 May 2007 10:47:46 -0700 (PDT) Message-ID: <3f85ef270705211047v4fdc6b8ex80e21bd7e4be9b0d@mail.gmail.com> Date: Mon, 21 May 2007 18:47:46 +0100 From: "=?UTF-8?Q?Jos=C3=A9_Costa?=" To: gentoo-server@lists.gentoo.org Subject: Re: [gentoo-server] Best practices in managing large server groups In-Reply-To: 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=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4650937E.80301@spamcop.net> <4650BCC7.60909@vanalteren.nl> <246510DE-93FF-46CD-AF10-70C53C8442A7@rogers.com> <4651C876.2@routedtechnologies.com> X-Archives-Salt: 048280ae-05e1-4e5b-aaea-08e85a310c2c X-Archives-Hash: aaf963d94e1cb85ef12e3a27977a1e08 try portage-utils. they are in C. On 5/21/07, Ronan Mullally wrote: > On Mon, 21 May 2007, Ryan Gibbons wrote: > > > I believe you will still need a tree either way. > > > > I would just have the master server share it's portage tree over nfs, and then > > when you update the nodes of the cluster, just mount the nfs share, run your > > emerge system or world or whatever, and then when you are finished umount the > > nfs share. > > > > I imagine this could be done easily via scripts, complete with error checking > > for bad mounts bad emerges etc. > > That's what I figured. Okay, last question - how do I stop emerge trying > to update the compiler-less systems to include development tools like gcc? > I presume tweaking the profile is the way to do it. Is there a stock > profile that already has these excluded? > > > -Ronan > -- > gentoo-server@gentoo.org mailing list > > -- gentoo-server@gentoo.org mailing list