public inbox for gentoo-server@lists.gentoo.org
 help / color / mirror / Atom feed
From: "José Costa" <meetra@gmail.com>
To: gentoo-server@lists.gentoo.org
Subject: Re: [gentoo-server] Best practices in managing large server groups
Date: Mon, 21 May 2007 18:54:20 +0100	[thread overview]
Message-ID: <3f85ef270705211054v4f9cf3bcwe8999be4a6b5d4ce@mail.gmail.com> (raw)
In-Reply-To: <3f85ef270705211047v4fdc6b8ex80e21bd7e4be9b0d@mail.gmail.com>

ups, replied for the wrong email "question".

how about dealing with /var/*/portage and db stuff?

On 5/21/07, José Costa <meetra@gmail.com> wrote:
> try portage-utils. they are in C.
>
> On 5/21/07, Ronan Mullally <ronan@iol.ie> 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
> >
> >
>

  reply	other threads:[~2007-05-21 17:57 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
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 [this message]
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=3f85ef270705211054v4f9cf3bcwe8999be4a6b5d4ce@mail.gmail.com \
    --to=meetra@gmail.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