X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C6FE25.9A907427@onstor-exch02.onstor.net>; Wed, 1 Nov 2006 18:21:28 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C6FE25.9A907427"
Content-class: urn:content-classes:message
Subject: RE: "how to" build and load doc
Date: Wed, 1 Nov 2006 18:21:28 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E01335E49@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: "how to" build and load doc
thread-index: Acb+I1F434oC7LYySPyBxeIQMO0DZAAAI87AAAAZX6M=
References: <BB375AF679D4A34E9CA8DFA650E2B04E01384180@onstor-exch02.onstor.net>
From: "Ken Renshaw" <ken.renshaw@onstor.com>
To: "Tim Gardner" <tim.gardner@onstor.com>,
	"Brian DeForest" <brian.deforest@onstor.com>,
	"dl-Software" <dl-software@onstor.com>,
	"Maxim Kozlovsky" <maxim.kozlovsky@onstor.com>,
	"Jonathan Goldick" <jonathan.goldick@onstor.com>
Cc: "dl-QE-staff" <dl-QE-staff@onstor.com>

This is a multi-part message in MIME format.

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

I'll collect what I have and post it as well. there's actually a fair =
amount it's just spread all over ( and some existing in email HOWTOs, =
for example ). Ideally this should cover everything from Perforce =
initial setup, building EverON images and getting them loaded and =
running on filers, through how to debug filers, etc.=20

Agree the wiki is probably the best place to coallesce all of this, and =
at least partially agree the new employees should document their =
experiences, i.e. generate/update HOWTO docs as needed. But we, all of =
us who know the processes and tools best, should write the drafts or =
supply the initial inputs to the new guys.

Thanks for driving this BTW.

-Ken


-----Original Message-----
From: Tim Gardner
Sent: Wed 11/1/2006 6:10 PM
To: Brian DeForest; dl-Software; Maxim Kozlovsky; Jonathan Goldick; Ken =
Renshaw
Subject: RE: "how to" build and load doc
=20
The correct place for this info is the wiki. Some of it is already =
there. More needs to be added.
I have asked Andy to add new info to the wiki if what he needs is not =
there. Best persons to write the
howto docs are the new employees.


_____________________________________________
From: Brian DeForest=20
Sent: Wednesday, November 01, 2006 6:05 PM
To: dl-Software; Maxim Kozlovsky; Jonathan Goldick; Ken Renshaw
Subject: "how to" build and load doc

One thing every new engineer immediately needs is a "how to" guide to =
start building and downloading images.   We have discussed this in the =
past.    If you know of any existing documents describing how to build =
and download/mount your build, please forward pointers.

Otherwise, one possibility is to checkin a README file in the top level =
nfx-tree.   This would include things like:
1.	make command line options
2.	ways to install/mount binaries
3.	tips, known problems, etc.
4.	longer term:   high level functional description of each directory  =
(possibly a different file)

Thoughts?   Any volunteers to create a first draft?   I'll bring in some =
Halloween candy for the first volunteer, or treat him/her to a beverage =
of choice in the breakroom.  :-)

Brian



------_=_NextPart_001_01C6FE25.9A907427
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.7650.28">
<TITLE>RE: &quot;how to&quot; build and load doc</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>I'll collect what I have and post it as well. there's =
actually a fair amount it's just spread all over ( and some existing in =
email HOWTOs, for example ). Ideally this should cover everything from =
Perforce initial setup, building EverON images and getting them loaded =
and running on filers, through how to debug filers, etc.<BR>
<BR>
Agree the wiki is probably the best place to coallesce all of this, and =
at least partially agree the new employees should document their =
experiences, i.e. generate/update HOWTO docs as needed. But we, all of =
us who know the processes and tools best, should write the drafts or =
supply the initial inputs to the new guys.<BR>
<BR>
Thanks for driving this BTW.<BR>
<BR>
-Ken<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: Tim Gardner<BR>
Sent: Wed 11/1/2006 6:10 PM<BR>
To: Brian DeForest; dl-Software; Maxim Kozlovsky; Jonathan Goldick; Ken =
Renshaw<BR>
Subject: RE: &quot;how to&quot; build and load doc<BR>
<BR>
The correct place for this info is the wiki. Some of it is already =
there. More needs to be added.<BR>
I have asked Andy to add new info to the wiki if what he needs is not =
there. Best persons to write the<BR>
howto docs are the new employees.<BR>
<BR>
<BR>
_____________________________________________<BR>
From: Brian DeForest<BR>
Sent: Wednesday, November 01, 2006 6:05 PM<BR>
To: dl-Software; Maxim Kozlovsky; Jonathan Goldick; Ken Renshaw<BR>
Subject: &quot;how to&quot; build and load doc<BR>
<BR>
One thing every new engineer immediately needs is a &quot;how to&quot; =
guide to start building and downloading images.&nbsp;&nbsp; We have =
discussed this in the past.&nbsp;&nbsp;&nbsp; If you know of any =
existing documents describing how to build and download/mount your =
build, please forward pointers.<BR>
<BR>
Otherwise, one possibility is to checkin a README file in the top level =
nfx-tree.&nbsp;&nbsp; This would include things like:<BR>
1.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; make command line options<BR>
2.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ways to install/mount binaries<BR>
3.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; tips, known problems, etc.<BR>
4.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; longer term:&nbsp;&nbsp; high level =
functional description of each directory&nbsp; (possibly a different =
file)<BR>
<BR>
Thoughts?&nbsp;&nbsp; Any volunteers to create a first =
draft?&nbsp;&nbsp; I'll bring in some Halloween candy for the first =
volunteer, or treat him/her to a beverage of choice in the =
breakroom.&nbsp; :-)<BR>
<BR>
Brian<BR>
<BR>
<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C6FE25.9A907427--
