AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<richard.beck@onstor.com>,<larry.scheer@onstor.com>,<tim.gardner@onstor.com>,<maxim.kozlovsky@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/andys@onstor.net@onstor-exch02.onstor.net/INBOX	0	BB375AF679D4A34E9CA8DFA650E2B04E032587A0@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Wed, 4 Apr 2007 10:16:24 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Richard Beck" <richard.beck@onstor.com>
Cc: "Larry Scheer" <larry.scheer@onstor.com>, "Tim Gardner"
 <tim.gardner@onstor.com>, "Maxim Kozlovsky" <maxim.kozlovsky@onstor.com>
Subject: Re: documentation of changes to cougar branch
Message-ID: <20070404101624.43be16a6@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E032587A0@onstor-exch02.onstor.net>
References: <BB375AF679D4A34E9CA8DFA650E2B04E022156F4@onstor-exch02.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04E032587A0@onstor-exch02.onstor.net>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

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