public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Al <oss.elmar@googlemail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Shared libraries in Gentoo
Date: Thu, 9 Sep 2010 13:50:27 +0200	[thread overview]
Message-ID: <AANLkTimDwQG+NL5b4kzCcxahPTnzOPNF_JX_hnBG=XXa@mail.gmail.com> (raw)
In-Reply-To: <201009091056.39057.alan.mckinnon@gmail.com>

> My beef with portage in my specific production setup is the amount of work it
> takes my guys to keep everything up to date. We don't have 150 identical
> servers in a farm (I'd love that and would switch to Gentoo immediately if it
> were). I have 130 completely different configs and uses for those servers.
>

How about migrating them one-by-one to CentOs first and in a second
step to Gentoo?

Sure every servers migration is work. But there will be routine once
you have migrated 10.

Having a uniform serverfarm should pay the efforts after a reasonable time.

Al



  reply	other threads:[~2010-09-09 11:51 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-06 18:28 [gentoo-user] Shared libraries in Gentoo Al
2010-09-06 20:30 ` [gentoo-user] " Nikos Chantziaras
2010-09-06 21:24   ` Al
2010-09-06 21:38     ` Al
2010-09-06 22:49     ` Nikos Chantziaras
2010-09-07  1:00       ` Al
2010-09-09  3:11     ` Enrico Weigelt
2010-09-06 22:43 ` walt
2010-09-07  0:39   ` Al
2010-09-07  3:47     ` Ajai Khattri
2010-09-07  9:33       ` Al
2010-09-07 16:13         ` Ajai Khattri
2010-09-07 16:40           ` Alan McKinnon
2010-09-07 18:15             ` Al
2010-09-07 21:20               ` Alan McKinnon
2010-09-07 23:51                 ` Al
2010-09-08 16:07                 ` Al
2010-09-09  2:36                   ` Enrico Weigelt
2010-09-09  8:55                     ` Al
2010-09-10  1:00                       ` Enrico Weigelt
2010-09-09 10:28                     ` Al
2010-09-09 11:12                       ` [gentoo-user] " Andrea Conti
2010-09-09 12:28                         ` Al
2010-09-10  0:40                         ` Enrico Weigelt
2010-09-10  0:38                       ` [gentoo-user] " Enrico Weigelt
2010-09-09  0:56                 ` Enrico Weigelt
2010-09-09  8:56                   ` Alan McKinnon
2010-09-09 11:50                     ` Al [this message]
2010-09-09 12:25                       ` Alan McKinnon
2010-09-09 13:20                         ` Al
2010-09-09 13:54                           ` Alan McKinnon
2010-09-09 15:12                         ` Neil Bothwick
2010-09-09 15:26                           ` Alan McKinnon
2010-09-09 16:28                             ` Neil Bothwick
2010-09-09 21:03                             ` Graham Murray
2010-09-09 23:49                     ` Enrico Weigelt
2010-09-10 16:43                       ` Florian Philipp
2010-09-10 19:02                         ` Alan McKinnon
2010-09-10 23:25                         ` walt
2010-09-09  2:52               ` Enrico Weigelt
2010-09-09 15:02                 ` Al
2010-09-10  0:19                   ` Enrico Weigelt
2010-09-10 12:27                     ` Al
2010-09-12 21:30                       ` Enrico Weigelt
2010-09-12 22:47                         ` Al
2010-09-13  1:11                           ` Enrico Weigelt
2010-09-07 19:12           ` Al
2010-09-08 19:29   ` Al

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='AANLkTimDwQG+NL5b4kzCcxahPTnzOPNF_JX_hnBG=XXa@mail.gmail.com' \
    --to=oss.elmar@googlemail.com \
    --cc=gentoo-user@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