[MITgcm-devel] RE: [MITgcm-support] daily snap-shots insteadofCVS pserver
Chris Hill
cnh at mit.edu
Mon Jun 7 09:45:22 EDT 2004
I'll see if we can get Brian to vet some hardware.
Chris
> -----Original Message-----
> From: mitgcm-devel-bounces at mitgcm.org
> [mailto:mitgcm-devel-bounces at mitgcm.org] On Behalf Of Alistair Adcroft
> Sent: Friday, June 04, 2004 11:59 PM
> To: MITgcm-devel at mitgcm.org
> Subject: RE: [MITgcm-devel] RE: [MITgcm-support] daily
> snap-shots insteadofCVS pserver
>
> Chris?
>
> --
> Dr Alistair Adcroft http://www.mit.edu/~adcroft
> MIT Climate Modeling Initiative tel: (617) 253-5938
> EAPS 54-1624, 77 Massachusetts Ave, Cambridge, MA, USA
>
> -----Original Message-----
> From: mitgcm-devel-bounces at mitgcm.org
> [mailto:mitgcm-devel-bounces at mitgcm.org] On Behalf Of Ed Hill
> Sent: Friday, June 04, 2004 9:52 PM
> To: MITgcm-devel
> Subject: Re: [MITgcm-devel] RE: [MITgcm-support] daily
> snap-shots insteadof CVS pserver
>
>
> On Fri, 2004-06-04 at 21:20, Alistair Adcroft wrote:
> > That's pretty inconvenient for anyone who has local code
> modifications
> > of their own. How long is pserver going to be out of commission?
>
>
> Hi Alistair,
>
> So how soon can we scrounge up enough parts to build a new
> machine? I tried two of the old PIII systems from 1725 and
> encountered multiple dead drives and either a dead MB or
> power supply. Then the P4 parts that Chris gave us (Matt of
> TS assembled them) wouldn't even POST. Its not encouraging.
>
> And as Greg pointed out: isn't it moronic to even try to
> assemble one of our more important servers from a bunch of
> old, dodgy crap?
>
> Ed
>
> --
> Edward H. Hill III, PhD
> office: MIT Dept. of EAPS; Rm 54-1424; 77 Massachusetts Ave.
> Cambridge, MA 02139-4307
> emails: eh3 at mit.edu ed at eh3.com
> URLs: http://web.mit.edu/eh3/ http://eh3.com/
> phone: 617-253-0098
> fax: 617-253-4464
>
>
> _______________________________________________
> MITgcm-devel mailing list
> MITgcm-devel at mitgcm.org
> http://dev.mitgcm.org/mailman/listinfo/mitgcm-devel
>
More information about the MITgcm-devel
mailing list