X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C77654.F5C6CB17@onstor-exch02.onstor.net>; Tue, 3 Apr 2007 18:02:47 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: documentation of changes to cougar branch
Date: Tue, 3 Apr 2007 18:02:47 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E022156F4@onstor-exch02.onstor.net>
In-Reply-To: <20070403170100.5cd12df5@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: documentation of changes to cougar branch
Thread-Index: Acd2TFR32zAh2vdOShCiCHvGtk0/dQAAW+xQ
From: "Larry Scheer" <larry.scheer@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>
Cc: "Tim Gardner" <tim.gardner@onstor.com>,
	"Maxim Kozlovsky" <maxim.kozlovsky@onstor.com>,
	"Richard Beck" <richard.beck@onstor.com>

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.

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:

Linux/:
  arch/  drivers/  include/  init/  kernel/  net/

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.

I added Pkgs/ and pkg-tools/ This made sense for the package stuff.

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.

Max mentioned he doesn't like the location of the neteee includes. But I
simply used what was there.

But to answer your REAL question, yes, I will document how things work,
probably in a wiki page.

Larry


-----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

Hi Larry,

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.

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.  ~:^)

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.

Thanks,

a
