From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: overseers@gcc.gnu.org, Gerald Pfeifer <gerald@pfeifer.com>
Subject: Re: Any plans to upgrade from RHEL 4?
Date: Sun, 15 Aug 2010 18:57:00 -0000 [thread overview]
Message-ID: <20100815185745.GB26993@ednor.casa.cgf.cx> (raw)
In-Reply-To: <alpine.LNX.2.00.1008152043530.10053@acrux.dbai.tuwien.ac.at>
On Sun, Aug 15, 2010 at 08:49:46PM +0200, Gerald Pfeifer wrote:
>When I did my patch to add md5sums to the announcements of GCC
>snapshots what I had tested on my notebook actually failed to work on
>gcc.gnu.org -- openssl does not yet support sha256 there.
>
>That made me realize that we are still running RHEL 4 which was first
>released early in 2005. I understand there is still a bit of life in
>that platform (and I do understand Enterprise Linux, kind of key to my
>day job <g>), but still I wonder -- are there any plans moving to RHEL
>5, say?
A while ago, I started up a virtual machine on one of our almost useless
"backup" sourceware systems to see what would be required to upgrade. I
was actually thinking of switching to Fedora since it allows you to more
easily upgrade between releases.
fche and I got into a (very) mild disagreement on that course of action so
I haven't pursued it much since then.
I agree that we need to upgrade but it really would be nice to move to
a new system at that time too.
I wonder if we could get some kind organization to donate new hardware.
That would make the switchover much easier.
We do have access to a google-sponsored machine but its configuration is
not as hefty as the current sourceware so I don't think we'd want to
move there.
cgf
next prev parent reply other threads:[~2010-08-15 18:57 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 [this message]
2010-08-15 19:04 ` Frank Ch. Eigler
2010-08-15 19:12 ` Christopher Faylor
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=20100815185745.GB26993@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@sourceware.org \
--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).