AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20070516114843.234801f6@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<ken.renshaw@onstor.com>,<larry.scheer@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	BB375AF679D4A34E9CA8DFA650E2B04E02F3D0B3@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Wed, 16 May 2007 11:50:05 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Ken Renshaw" <ken.renshaw@onstor.com>
Cc: Larry Scheer <larry.scheer@onstor.com>
Subject: Re: 2.2.2.5  w/n boot
Message-ID: <20070516115005.0d9e996a@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E02F3D0B3@onstor-exch02.onstor.net>
References: <BB375AF679D4A34E9CA8DFA650E2B04EEACB42@onstor-exch02.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04E03C0BB39@onstor-exch02.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04E02F3D0B0@onstor-exch02.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04E02F3D0B3@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

Hi Guys,

I'm sure I'm being ignorant again, but I still don't see why we don't
build BSD along with everything else, from scratch, for each and every
release, submittal, nightly build, freckle on my @ss, and so on.  Is
there some reason we don't just move to that model, so we won't ever
have these problems ever again?  My ignorance is a product of a troubled
childhood, so don't be insensitive you guys.  You know how you are.

a


On Wed, 16 May 2007 11:43:31 -0700 "Ken Renshaw"
<ken.renshaw@onstor.com> wrote:

> From now on I will add a step in the build process for patches to do
> a quick file delta from the previous patch and include that in the
> build info. Hopefully that will help us flag these kinds of things
> before they leave the building. Thanks, 
> -Ken
> 
> ________________________________
> 
> From: Ken Renshaw
> Sent: Wed 5/16/2007 11:37 AM
> To: Ed Kwan; Huy Duong; David Crispin; Victor Carrell (Glasshouse);
> dl-cstech Cc: Danqing Jin; Erik Palomba; Ken Renshaw
> Subject: RE: 2.2.2.5 w/n boot
> 
> 
> Hello.
>  
> The last four patches have all been done with the same build of bsd:
>  
> [build@k2 Build-Trees]$ strings
> R2.2.2.3/R2.2.2.3-041807/nfx-tree/Build/bc/opt/Release/bsd | grep
> OpenBSD| grep BOBCAT @(#)OpenBSD 2.8 (BOBCAT) #0: Thu Jan 18 13:34:43
> PST 2007 [build@k2 Build-Trees]$ strings
> R2.2.2.4/R2.2.2.4-042507/nfx-tree/Build/bc/opt/Release/bsd | grep
> OpenBSD| grep BOBCAT @(#)OpenBSD 2.8 (BOBCAT) #0: Thu Jan 18 13:34:43
> PST 2007 [build@k2 Build-Trees]$ strings
> R2.2.2.5/R2.2.2.5-043007/nfx-tree/Build/bc/opt/Release/bsd | grep
> OpenBSD| grep BOBCAT @(#)OpenBSD 2.8 (BOBCAT) #0: Thu Jan 18 13:34:43
> PST 2007 [build@k2 Build-Trees]$ strings
> R2.2.2.6/R2.2.2.6-051407/nfx-tree/Build/bc/opt/Release/bsd | grep
> OpenBSD| grep BOBCAT @(#)OpenBSD 2.8 (BOBCAT) #0: Thu Jan 18 13:34:43
> PST 2007 This is not a matter of using the wrong BSD to package the
> patch. It's a case of someone corrupting the posted BSD images,
> probably by doing a p4 sync when /usr/openbsd.new was pointed to the
> 2.2.x BSD when they thought it was pointed to DeLorean. 
> 
> In the Notes section of CQ 19207 Danqing does a compare of the two
> files /etc/rc and /etc/mdrive_fstab and found they had parts of
> recent DeLorean changes grafted into them. These same pieces are in
> the posted BSD build for 2.2.x: /n/Build-Trees/BSD/openbsd-latest-22 
> I believe all we have to do to fix this is copy the correct
> 2.2.x /etc files into the posted 2.2.x BSD build and rebuild the
> patch tarfiles. Ed, you'd said spin 2.2.2.5 as 2.2.2.7, but isn't
> what we want to do is respin 2.2.2.6 as 2.2.2.7 with the
> corrected /etc files so they stay cumulative? Please confirm, then
> I'll go ahead and do this. Thanks, 
> -Ken
> 
> ________________________________
> 
> From: Ed Kwan
> Sent: Wed 5/16/2007 11:05 AM
> To: Huy Duong; David Crispin; Victor Carrell (Glasshouse); dl-cstech
> Cc: Ken Renshaw; Danqing Jin; Erik Palomba
> Subject: RE: 2.2.2.5 w/n boot
> 
> 
> 
> TED 19207.  Need to re-spin 2.2.2.5 (as 2.2.2.7) with the correct BSD.
> 
> > -----Original Message-----
> > From: Huy Duong
> > Sent: Wednesday, May 16, 2007 9:01 AM
> > To: David Crispin; Victor Carrell (Glasshouse); dl-cstech
> > Subject: Re: 2.2.2.5 w/n boot
> >
> > Victor file a bug. This is very serious I will escalate it.
> > -----------------------------------------
> > Huy Duong
> > ONStor Strategic Support Account Manager
> > Phone 408.963.2478
> > Cell    408.431.6803
> > http://support.onstor.com/
> > Sent From My Blackberry
> >
> >
> > -----Original Message-----
> > From: David Crispin
> > To: Victor Carrell (Glasshouse); dl-cstech
> > Sent: Wed May 16 08:48:45 2007
> > Subject: Re: 2.2.2.5  w/n boot
> >
> > I had the same thing yesterday. System upgrade, compare then reboot
> > -s and it never came back. This was in a remote data centre. A real
> > pain. It's still down.
> >
> > Regards,
> > David Crispin
> > Technical Services Manager
> > ONStor Ltd.
> > 07940 547895
> >
> > Sent from my Blackberry
> >
> > -----Original Message-----
> > From: Victor Carrell (Glasshouse)
> > To: dl-cstech
> > Sent: Wed May 16 07:41:42 2007
> > Subject: 2.2.2.5  w/n boot
> >
> > Hi All,
> >
> >
> >
> >             Can some one tell me the super secret step needed to
> > boot a 22xx 2.2.2.5 after an upgrade?
> >
> >
> >
> > We tried upgrading LA Health yesterday 2 systems 1 system twice.
> > Everything runs clean compare, md5 and version -s ok but will not
> > boot
> >
> >
> >
> > I tried the same upgrade from a local ftp server to our systems
> > in-house w/same results.
> >
> >
> >
> > Thanks
> >
> > Victor
> 
> 
> 
