X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C78703.D0A1B85C@onstor-exch02.onstor.net>; Tue, 24 Apr 2007 23:34:45 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C78703.D0A1B85C"
Content-class: urn:content-classes:message
Subject: mount point for flash initialization
Date: Tue, 24 Apr 2007 23:34:45 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E028FB40A@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: mount point for flash initialization
Thread-Index: AceHA9Ch59Q5AH8aRQewO2gmLwGeBg==
From: "Mike Lee" <mike.lee@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>
Cc: "Larry Scheer" <larry.scheer@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C78703.D0A1B85C
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Andy:

I'm trying to follow the instruction for the flash initialization on the =
wiki page, and I see that you recently changed the NFS destination in =
the example
from:
 10.0.0.236:/nx-d_buildup/build-trees/
to:
 10.0.0.236:/n/build-trees/

Wouldn't nx-d_buildup be a better example, since it is actually what =
needs to be specified in the mount command today, or will it be changed =
to the latter in near future?

-Mike

------_=_NextPart_001_01C78703.D0A1B85C
Content-Type: text/html;
	charset="iso-8859-1"
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=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7652.24">
<TITLE>mount point for flash initialization</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>Hi Andy:<BR>
<BR>
I'm trying to follow the instruction for the flash initialization on the =
wiki page, and I see that you recently changed the NFS destination in =
the example<BR>
from:<BR>
&nbsp;10.0.0.236:/nx-d_buildup/build-trees/<BR>
to:<BR>
&nbsp;10.0.0.236:/n/build-trees/<BR>
<BR>
Wouldn't nx-d_buildup be a better example, since it is actually what =
needs to be specified in the mount command today, or will it be changed =
to the latter in near future?<BR>
<BR>
-Mike<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C78703.D0A1B85C--
