AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20080131143504.76c459c1@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<sripal.surendiran@onstor.com>,<brian.deforest@onstor.com>,<tim.gardner@onstor.com>,<jonathan.goldick@onstor.com>,<sudharsan@onstor.com>,<narain.ramadass@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	BB375AF679D4A34E9CA8DFA650E2B04EC247B1@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Thu, 31 Jan 2008 14:37:05 -0800
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Sripal Surendiran (HCL)" <sripal.surendiran@onstor.com>
Cc: "Brian DeForest" <brian.deforest@onstor.com>, "Tim Gardner"
 <tim.gardner@onstor.com>, "Jonathan Goldick" <jonathan.goldick@onstor.com>,
 "Sudharsan Srinivasan" <sudharsan@onstor.com>, "Narain Ramadass"
 <narain.ramadass@onstor.com>
Subject: Re: Bobcat to Cougar migration document for review
Message-ID: <20080131143705.5d1d2aa0@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04EC247B1@onstor-exch02.onstor.net>
References: <BB375AF679D4A34E9CA8DFA650E2B04EC247B1@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 Thu, 31 Jan 2008 05:46:25 -0800 "Sripal Surendiran (HCL)"
<sripal.surendiran@onstor.com> wrote:

> Hi All,
>  
> PFA document that contains strategy for migrating from Bobcat to
> Cougar system. Please look into the document and let me know your
> thoughts. Regards
> Sripal.

Page 1

+  I haven't been able to read a bobcat compact flash in a linux system.
   Have you?

Page 2

+  Section 1, Line #11: the directory is the same -- it's the same code,
   after all.

+  Section 2, Assumptions and dependencies.  I don't agree with a lot of
   these assumptions and dependencies, like #2, #3, #4, #7, and #9.
   There is no reason why a migration should be dependent on FTI.  FTI
   can use it or whatever, but it should be modular, separate,
   preferably something that can be run from a bash prompt or nfxsh
   prompt.  A shell script would be fine in my opinion.


I agree with Tim, a proper func-spec document is most likely
warranted here.