X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C777B2.6993621B@onstor-exch02.onstor.net>; Thu, 5 Apr 2007 11:44:16 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C777B2.6993621B"
References: <BB375AF679D4A34E9CA8DFA650E2B04E022156F4@onstor-exch02.onstor.net><BB375AF679D4A34E9CA8DFA650E2B04E032587A0@onstor-exch02.onstor.net> <20070404101624.43be16a6@ripper.onstor.net>
Content-class: urn:content-classes:message
Subject: RE: documentation of changes to cougar branch
Date: Thu, 5 Apr 2007 11:43:43 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E032587A1@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: documentation of changes to cougar branch
Thread-Index: Acd23PlQ+UJkgzSGSySveOsUWvBA0gA1VzeD
From: "Richard Beck" <IMCEAEX-_O=ONSTOR_OU=FIRST+20ADMINISTRATIVE+20GROUP_CN=RECIPIENTS_CN=RICHARD+2EBECK@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>

This is a multi-part message in MIME format.

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


Yes - net/
-rb

-----Original Message-----
From: Andy Sharp
Sent: Wed 4/4/2007 10:16 AM
To: Richard Beck
Cc: Larry Scheer; Tim Gardner; Maxim Kozlovsky
Subject: Re: documentation of changes to cougar branch
=20
On Wed, 4 Apr 2007 09:50:24 -0700 "Richard Beck"
<richard.beck@onstor.com> wrote:

> I currently have code only in /net, so wherever /net ends up, I'll be
> OK with it. --Rich

Do you mean net/ ?

> -----Original Message-----
> From: Larry Scheer
> Sent: Tue 4/3/2007 6:02 PM
> To: Andy Sharp
> Cc: Tim Gardner; Maxim Kozlovsky; Richard Beck
> Subject: RE: documentation of changes to cougar branch
> =20
> My initial check-in or two without review were just to get some of
> the Makefiles and rpms in place. I initially bolted stuff in place
> based on where some parts were in the current cougar branch, such as
> how the linux tree was currently laid out. I did this knowing much of
> it will change.
>=20
> We need to review what the directory structure for your source should
> look like. The current linux directory structure was laid out by Dan
> Stein and I don't know if it still makes sense for you or Richard's
> stuff. This is what Dan laid out:
>=20
> Linux/:
>   arch/  drivers/  include/  init/  kernel/  net/
>=20
> This appears to be a possible layout for the kernel sources and a
> possible area for shared code between nfx-tree and the kernel. This
> is where Richard's previous work on neteee is found. It can be
> reorganized to better suit our needs. If this looks like the layout
> you expect for your code then you should use these directories for
> your components and new ones if needed.
>=20
> I added Pkgs/ and pkg-tools/ This made sense for the package stuff.
>=20
> Pkgs contain the RPMs at this time and a place holder for debian
> packages but none are checked in. The directory pkg-tools contain
> checked-in versions of the tools you gave me that fetch and
> manipulate debian packages.
>=20
> Max mentioned he doesn't like the location of the neteee includes.
> But I simply used what was there.
>=20
> But to answer your REAL question, yes, I will document how things
> work, probably in a wiki page.
>=20
> Larry
>=20
>=20
> -----Original Message-----
> From: Andy Sharp=20
> Sent: Tuesday, April 03, 2007 5:01 PM
> To: Larry Scheer
> Cc: Tim Gardner; Maxim Kozlovsky
> Subject: documentation of changes to cougar branch
>=20
> Hi Larry,
>=20
> You've checked in a number of changes and additions to the cougar
> branch without review.  Consequently, nobody knows how the stuff you
> checked in works, where it lives, what the operating theory is ...
> etc.
>=20
> Could you write a _brief_ design document that captures all this
> information?  Where things are checked in, how the makefiles work, and
> so on?  Feel free to use whatever format makes you happy: wiki,
> open-document-format, or plain text file.  ~:^)
>=20
> That would be a big help.  I'm looking for somewhere to check in my
> kernel bits, but I really don't know where to start.  This will help
> me there but also in other things.
>=20
> Thanks,
>=20
> a
>=20


------_=_NextPart_001_01C777B2.6993621B
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>RE: documentation of changes to cougar branch</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<BR>

<P><FONT SIZE=3D2>Yes - net/<BR>
-rb<BR>
<BR>
-----Original Message-----<BR>
From: Andy Sharp<BR>
Sent: Wed 4/4/2007 10:16 AM<BR>
To: Richard Beck<BR>
Cc: Larry Scheer; Tim Gardner; Maxim Kozlovsky<BR>
Subject: Re: documentation of changes to cougar branch<BR>
<BR>
On Wed, 4 Apr 2007 09:50:24 -0700 &quot;Richard Beck&quot;<BR>
&lt;richard.beck@onstor.com&gt; wrote:<BR>
<BR>
&gt; I currently have code only in /net, so wherever /net ends up, I'll =
be<BR>
&gt; OK with it. --Rich<BR>
<BR>
Do you mean net/ ?<BR>
<BR>
&gt; -----Original Message-----<BR>
&gt; From: Larry Scheer<BR>
&gt; Sent: Tue 4/3/2007 6:02 PM<BR>
&gt; To: Andy Sharp<BR>
&gt; Cc: Tim Gardner; Maxim Kozlovsky; Richard Beck<BR>
&gt; Subject: RE: documentation of changes to cougar branch<BR>
&gt;&nbsp;<BR>
&gt; My initial check-in or two without review were just to get some =
of<BR>
&gt; the Makefiles and rpms in place. I initially bolted stuff in =
place<BR>
&gt; based on where some parts were in the current cougar branch, such =
as<BR>
&gt; how the linux tree was currently laid out. I did this knowing much =
of<BR>
&gt; it will change.<BR>
&gt;<BR>
&gt; We need to review what the directory structure for your source =
should<BR>
&gt; look like. The current linux directory structure was laid out by =
Dan<BR>
&gt; Stein and I don't know if it still makes sense for you or =
Richard's<BR>
&gt; stuff. This is what Dan laid out:<BR>
&gt;<BR>
&gt; Linux/:<BR>
&gt;&nbsp;&nbsp; arch/&nbsp; drivers/&nbsp; include/&nbsp; init/&nbsp; =
kernel/&nbsp; net/<BR>
&gt;<BR>
&gt; This appears to be a possible layout for the kernel sources and =
a<BR>
&gt; possible area for shared code between nfx-tree and the kernel. =
This<BR>
&gt; is where Richard's previous work on neteee is found. It can be<BR>
&gt; reorganized to better suit our needs. If this looks like the =
layout<BR>
&gt; you expect for your code then you should use these directories =
for<BR>
&gt; your components and new ones if needed.<BR>
&gt;<BR>
&gt; I added Pkgs/ and pkg-tools/ This made sense for the package =
stuff.<BR>
&gt;<BR>
&gt; Pkgs contain the RPMs at this time and a place holder for =
debian<BR>
&gt; packages but none are checked in. The directory pkg-tools =
contain<BR>
&gt; checked-in versions of the tools you gave me that fetch and<BR>
&gt; manipulate debian packages.<BR>
&gt;<BR>
&gt; Max mentioned he doesn't like the location of the neteee =
includes.<BR>
&gt; But I simply used what was there.<BR>
&gt;<BR>
&gt; But to answer your REAL question, yes, I will document how =
things<BR>
&gt; work, probably in a wiki page.<BR>
&gt;<BR>
&gt; Larry<BR>
&gt;<BR>
&gt;<BR>
&gt; -----Original Message-----<BR>
&gt; From: Andy Sharp<BR>
&gt; Sent: Tuesday, April 03, 2007 5:01 PM<BR>
&gt; To: Larry Scheer<BR>
&gt; Cc: Tim Gardner; Maxim Kozlovsky<BR>
&gt; Subject: documentation of changes to cougar branch<BR>
&gt;<BR>
&gt; Hi Larry,<BR>
&gt;<BR>
&gt; You've checked in a number of changes and additions to the =
cougar<BR>
&gt; branch without review.&nbsp; Consequently, nobody knows how the =
stuff you<BR>
&gt; checked in works, where it lives, what the operating theory is =
...<BR>
&gt; etc.<BR>
&gt;<BR>
&gt; Could you write a _brief_ design document that captures all =
this<BR>
&gt; information?&nbsp; Where things are checked in, how the makefiles =
work, and<BR>
&gt; so on?&nbsp; Feel free to use whatever format makes you happy: =
wiki,<BR>
&gt; open-document-format, or plain text file.&nbsp; ~:^)<BR>
&gt;<BR>
&gt; That would be a big help.&nbsp; I'm looking for somewhere to check =
in my<BR>
&gt; kernel bits, but I really don't know where to start.&nbsp; This =
will help<BR>
&gt; me there but also in other things.<BR>
&gt;<BR>
&gt; Thanks,<BR>
&gt;<BR>
&gt; a<BR>
&gt;<BR>
<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C777B2.6993621B--
