public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: "Frank Ch. Eigler" <fche@redhat.com>,
	overseers@gcc.gnu.org, Gerald Pfeifer <gerald@pfeifer.com>
Subject: Re: Any plans to upgrade from RHEL 4?
Date: Sun, 15 Aug 2010 19:12:00 -0000	[thread overview]
Message-ID: <20100815191201.GC26993@ednor.casa.cgf.cx> (raw)
In-Reply-To: <20100815190403.GB7080@redhat.com>

On Sun, Aug 15, 2010 at 03:04:03PM -0400, Frank Ch. Eigler wrote:
>Hi -
>
>On Sun, Aug 15, 2010 at 02:57:45PM -0400, Christopher Faylor wrote:
>
>> [...]
>> I agree that we need to upgrade but it really would be nice to move to
>> a new system at that time too.
>
>Yeah, if only...

I don't know why this is inconceivable.  We've already done it two
(three?) times.

>> I wonder if we could get some kind organization to donate new hardware.
>> That would make the switchover much easier.
>
>Yeah, or else a multi-day extended downtime, with a robust
>backup/snapshot of the root partitions so we can undo any
>experimentation safely.
>
>We could live-upgrade server3 to use it as a guinea-pig, for it runs
>no essential services right now.  I'd advise RHEL5 or even 6 (beta, or
>we could wait a little more) as opposed to Fedora, since the latter
>not only permits but forces regular OS upgrades.  I'd rather not touch
>the guts of the machine again for a few years after the next change.

And the debate continues...

I think we've already seen the problems with sitting on a release for
several years.  I'd rather have the flexibility of being able to update
easily rather than painfully.  I have no problem with updating every
couple of years, notwithstanding personal bus impaction.

If we had two similar systems rather than the current foisted-upon-us
one system with two nearly useless lesser systems then we could do this
easily.

Actually, I guess we could do it with one system, a huge disk, lots of
memory, and the ability to run a virtual machine which mirrors its host.

cgf

      reply	other threads:[~2010-08-15 19:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-15 18:49 Gerald Pfeifer
2010-08-15 18:57 ` Christopher Faylor
2010-08-15 19:04   ` Frank Ch. Eigler
2010-08-15 19:12     ` Christopher Faylor [this message]

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=20100815191201.GC26993@ednor.casa.cgf.cx \
    --to=cgf-use-the-mailinglist-please@sourceware.org \
    --cc=fche@redhat.com \
    --cc=gerald@pfeifer.com \
    --cc=overseers@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).