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 1HqBkM-0007sU-Ep for garchives@archives.gentoo.org; Mon, 21 May 2007 17:32:38 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.14.0/8.14.0) with SMTP id l4LHW3lw006252; Mon, 21 May 2007 17:32:03 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 l4LHTRpB002884 for ; Mon, 21 May 2007 17:29:27 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 8D5CC17828 for ; Mon, 21 May 2007 18:29:27 +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 A7A752F4E for ; Mon, 21 May 2007 18:29:26 +0100 (BST) Date: Mon, 21 May 2007 18:29:26 +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: <4651C876.2@routedtechnologies.com> Message-ID: References: <4650937E.80301@spamcop.net> <4650BCC7.60909@vanalteren.nl> <246510DE-93FF-46CD-AF10-70C53C8442A7@rogers.com> <4651C876.2@routedtechnologies.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: 98511084-4f25-4f6c-8efc-cea35ef5fe5c X-Archives-Hash: 42e4b53424f1bbe2a7b4b2c97d1f4e2b 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