X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C8264F.19EC0CA1@onstor-exch02.onstor.net>; Tue, 13 Nov 2007 15:44:15 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: Cougar is ready
Date: Tue, 13 Nov 2007 15:44:15 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E068839F8@onstor-exch02.onstor.net>
In-Reply-To: <20071113154002.03c0ca9f@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Cougar is ready
Thread-Index: AcgmToL3sQKdV5wpRg6m+wQFPNGf9AAAByMA
References: <BB375AF679D4A34E9CA8DFA650E2B04E06883511@onstor-exch02.onstor.net> <20071113154002.03c0ca9f@ripper.onstor.net>
From: "Brian Stark" <brian.stark@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>

OK, good to hear.  I got all confused because I told Max his system was
the lower of the 2, which wasn't the case.  I had a 50/50 chance on
this, and you know how that goes. =20

Since I kept your CF with the system that you're now using, it's
possible the problem with Max's setup is the CF.  I've mentioned that to
him, so he'll take it from here.


Brian

=20

> -----Original Message-----
> From: Andy Sharp=20
> Sent: Tuesday, November 13, 2007 3:40 PM
> To: Brian Stark
> Subject: Re: Cougar is ready
>=20
> On Mon, 12 Nov 2007 18:32:33 -0800 "Brian Stark"
> <brian.stark@onstor.com> wrote:
>=20
> > Andy,
> >=20
> > Your Cougar is wired up in the Elab as follows:
> >=20
> > SSC IP 			10.2.10.8
> > SSC terminal		10.2.10.235 9044
> > TXRX0 terminal 		10.2.10.235 9047
> > TXRX1 terminal		10.2.10.235 9046
> > FP terminal 		10.2.10.235 9045
> >=20
> > John is still working on remote power cycling, and this should be=20
> > ready to go tomorrow.  I swapped your CF over to this=20
> system, so let=20
> > me know if you're seeing any issues accessing it from Linux.
> >=20
> >=20
> > Thanks,
> > Brian
> >=20
>=20
>=20
> Sorry for doubting you, you did indeed give me Max's.  ~:^) =20
> Next time I'll know to doubt Max instead.  The problem has=20
> followed him to his cougar, so no hardware problem to worry=20
> about.  I built and booted a clean check out of the kernel=20
> and everything works as advertised so the problem is all his.
>=20
> Cheers,
>=20
> a
>=20
