X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7EC26.47329D54@onstor-exch02.onstor.net>; Fri, 31 Aug 2007 15:25:55 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7EC26.47329D54"
Content-class: urn:content-classes:message
Subject: RE: cougar flash
Date: Fri, 31 Aug 2007 15:25:54 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E054B3986@onstor-exch02.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E054B3957@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: cougar flash
Thread-Index: AcfsIDPCFx+M0ubVRgWXvna4awa0igAAN6Ng
References: <BB375AF679D4A34E9CA8DFA650E2B04E054B3957@onstor-exch02.onstor.net>
From: "Brian Stark" <brian.stark@onstor.com>
To: "Tim Gardner" <tim.gardner@onstor.com>
Cc: "Andy Sharp" <andy.sharp@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7EC26.47329D54
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Tim,

Given our past discussions, I was not planning to go to 1GB on Cougar.
According to Andy, we have a ton of space available in the 512MB flash
today, especially after the flash was re-partitioned.  We talked about
this is a meeting a while back and decided we didn't need to go to 1GB
after all.  If the move to Linux changes that, then shipping 1GB is
fine.  Since we won't be moving Bobcat over to Linux in the field, we at
least don't have to worry about upgrading 512MB flashes to 1GB on the
installed base.

I'll have quotes available on the 1GB flash for Tuesday.  The cost delta
is not that big, but every penny that we save will help.


Brian


> _____________________________________________=20
> From: 	Tim Gardner =20
> Sent:	Friday, August 31, 2007 3:42 PM
> To:	Brian Stark
> Subject:	cougar flash
>=20
> =09
> Brian,
>=20
> Is the current plan to ship Cougar with a 1GB flash?
> I think that we will need 1GB. Although it may be possible to shoe
> horn everything into a smaller flash,
> it would be much easier to initially ship with the larger flash and
> possibly sometime in the future
> go to a smaller flash if the cost savings justify it. In the Tuesday
> meeting we plan to talk about
> the process of building the image that goes on a flash as well as the
> whole system upgrade
> process. Flash size is a part of this discussion. It would be useful
> to understand the difference
> in cost between 512MB and 1GB if you have that data available.
>=20
> Tim

------_=_NextPart_001_01C7EC26.47329D54
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7652.24">
<TITLE>RE: cougar flash</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Tim,</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Given our past =
discussions, I was not planning to go to 1GB on Cougar.&nbsp; According =
to Andy, we have a ton of space available in the 512MB flash today, =
especially after the flash was re-partitioned.&nbsp; We talked about =
this is a meeting a while back and decided we didn't need to go to 1GB =
after all.&nbsp; If the move to Linux changes that, then shipping 1GB is =
fine.&nbsp; Since we won't be moving Bobcat over to Linux in the field, =
we at least don't have to worry about upgrading 512MB flashes to 1GB on =
the installed base.</FONT></P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">I'll have quotes =
available on the 1GB flash for Tuesday.&nbsp; The cost delta is not that =
big, but every penny that we save will help.</FONT></P>
<BR>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Brian</FONT>
</P>
<BR>
<UL>
<P><FONT SIZE=3D1 =
FACE=3D"Tahoma">_____________________________________________ </FONT>

<BR><B><FONT SIZE=3D1 FACE=3D"Tahoma">From: &nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Tahoma">Tim Gardner&nbsp; </FONT>

<BR><B><FONT SIZE=3D1 FACE=3D"Tahoma">Sent:&nbsp;&nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Tahoma">Friday, August 31, 2007 3:42 PM</FONT>

<BR><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">To:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> <FONT SIZE=3D1 =
FACE=3D"Tahoma">Brian Stark</FONT>

<BR><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">Subject:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT>=
</B> <FONT SIZE=3D1 FACE=3D"Tahoma">cougar flash</FONT>
</P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20

<BR><FONT SIZE=3D2 FACE=3D"Arial">Brian,</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Is the current plan to ship Cougar with =
a 1GB flash?</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">I think that we will need 1GB. =
Although it may be possible to shoe horn everything into a smaller =
flash,</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">it would be much easier to initially =
ship with the larger flash and possibly sometime in the future</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">go to a smaller flash if the cost =
savings justify it. In the Tuesday meeting we plan to talk about</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">the process of building the image that =
goes on a flash as well as the whole system upgrade</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">process. Flash size is a part of this =
discussion. It would be useful to understand the difference</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">in cost between 512MB and 1GB if you =
have that data available.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Tim</FONT>
</P>
</UL>
</BODY>
</HTML>
------_=_NextPart_001_01C7EC26.47329D54--
