public inbox for gentoo-server@lists.gentoo.org
 help / color / mirror / Atom feed
From: Wendall Cada <wendallc@83864.com>
To: gentoo-server@lists.gentoo.org
Subject: Re: [gentoo-server]  Re: Best practices in managing large server groups
Date: Tue, 22 May 2007 18:33:16 -0700	[thread overview]
Message-ID: <1179883996.4646.3.camel@localhost> (raw)
In-Reply-To: <f2vm0r$die$1@sea.gmane.org>

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

On Tue, 2007-05-22 at 16:06 -0500, Charles Duffy wrote:
> Wendall Cada wrote:
> > I very much agree with his assessment here. This is what I do for binary
> > distribution to desktop systems. It is very effective. I have played
> > with Catalyst quite a bit, but agree that catalyst-2 is much more well
> > suited for this.
> 
> I'm sorry; which "this" are you referring to? I'm a little unclear on 
> whether what you're indicating that you use is Ramon's suggestion (of 
> using catalyst-2) or our senior sysadmin's suggestion (of using emerge, 
> set to output binary packages and target a chroot).

I use (of using emerge, set to output binary packages and target a
chroot) right now, as Ramon's senior sysadmin recommends. But am looking
into using catalyst-2 in the future.

Wendall
> 
> Thank you!
> 
-- 
Only wimps use tape backup: _real_ men just upload their important stuff
on ftp, and let the rest of the world mirror it ;)
        -- Linus Torvalds

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-05-23  1:36 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
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 [this message]
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=1179883996.4646.3.camel@localhost \
    --to=wendallc@83864.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