X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C89675.9DAA2120@onstor-exch02.onstor.net>; Fri, 4 Apr 2008 10:02:08 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C89675.9DAA2120"
Content-class: urn:content-classes:message
Subject: RE: bobcat linux unusable after fti
Date: Fri, 4 Apr 2008 10:02:08 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E042F013F@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: bobcat linux unusable after fti
Thread-Index: AciV7K4SWOa3M4fvSAyEJZL7AfNmpQAADD3AAAAfjrAAAkcfoAAd+tEQAAGTsfE=
References: <BB375AF679D4A34E9CA8DFA650E2B04E0941AB21@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E0941AB50@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E0941ACBD@onstor-exch02.onstor.net>
From: "Larry Scheer" <larry.scheer@onstor.com>
To: "Maxim Kozlovsky" <maxim.kozlovsky@onstor.com>,
	"Tim Gardner" <tim.gardner@onstor.com>,
	"dl-Cougar" <dl-Cougar@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C89675.9DAA2120
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Max,
  Maybe I am misunderstanding you. I can switch my bobcats to boot =
between Linux and BSD NFX releases without any issues. At least I was =
able to do this a week or so ago.  You should be able to just switch  =
your SSC prom environment and boot a BSD release from compact flash. Is =
that the difficulty you are having?

The problem I have is when I do switch to a Linux boot from an NFS root =
all the SSC daemons don't start.


-----Original Message-----
From: Maxim Kozlovsky
Sent: Fri 4/4/2008 9:16 AM
To: Tim Gardner; Larry Scheer; dl-Cougar
Subject: RE: bobcat linux unusable after fti
=20
It may sound like news to you, but there is still some number of bobcats =
out in the field so some of us have to work on that platform too. As far =
as the code goes bobcat and cougar linux are virtually identical, so =
unless you make a conscious effort to break one of them it is hard to =
accomplish. It will take me much more time to switch between bobcat and =
cougar every time I have to than to support both.

_____________________________________________
From: Tim Gardner=20
Sent: Thursday, April 03, 2008 6:54 PM
To: Maxim Kozlovsky; Larry Scheer; dl-Cougar
Subject: RE: bobcat linux unusable after fti


Once enough cougar systems became available and everyone moved to cougar
we stopped testing on bobcat linux. I don't want to spend time now =
fixing bobcat linux defects.
Use a cougar.

	_____________________________________________=20
	From: 	Maxim Kozlovsky =20
	Sent:	Thursday, April 03, 2008 4:51 PM
	To:	Larry Scheer; dl-Cougar
	Subject:	RE: bobcat linux unusable after fti

	You can't be serious, can you? You mean you've known that it is broken =
for a month and did not fix it or at the very least did not file a bug?=20

	I've been using bobcat linux up until now without any problems.

	_____________________________________________
	From: Larry Scheer=20
	Sent: Thursday, April 03, 2008 5:46 PM
	To: Maxim Kozlovsky; dl-Cougar
	Subject: RE: bobcat linux unusable after fti

	Bobcat Linux has been unusable for a month or so. The best I could do =
was boot Linux only but the minute I try to start pm and the ONStor =
processes weirdness ensues.

	_____________________________________________
	From: Maxim Kozlovsky=20
	Sent: Thursday, April 03, 2008 5:42 PM
	To: dl-Cougar
	Subject: bobcat linux unusable after fti

	Hello,

	I had some misguided notion couple of days ago that I should upgrade my =
bobcat linux booting from NFS to the latest rootfs and configure it from =
scratch. It has become unusable after I've configured it through nfxsh. =
Could somebody please fix this problem and actually test the fix by =
upgrading 10.2.10.2 to the latest code? I'd like to have my bobcat back. =


	Max


------_=_NextPart_001_01C89675.9DAA2120
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.7653.38">
<TITLE>RE: bobcat linux unusable after fti</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>Max,<BR>
&nbsp; Maybe I am misunderstanding you. I can switch my bobcats to boot =
between Linux and BSD NFX releases without any issues. At least I was =
able to do this a week or so ago.&nbsp; You should be able to just =
switch&nbsp; your SSC prom environment and boot a BSD release from =
compact flash. Is that the difficulty you are having?<BR>
<BR>
The problem I have is when I do switch to a Linux boot from an NFS root =
all the SSC daemons don't start.<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: Maxim Kozlovsky<BR>
Sent: Fri 4/4/2008 9:16 AM<BR>
To: Tim Gardner; Larry Scheer; dl-Cougar<BR>
Subject: RE: bobcat linux unusable after fti<BR>
<BR>
It may sound like news to you, but there is still some number of bobcats =
out in the field so some of us have to work on that platform too. As far =
as the code goes bobcat and cougar linux are virtually identical, so =
unless you make a conscious effort to break one of them it is hard to =
accomplish. It will take me much more time to switch between bobcat and =
cougar every time I have to than to support both.<BR>
<BR>
_____________________________________________<BR>
From: Tim Gardner<BR>
Sent: Thursday, April 03, 2008 6:54 PM<BR>
To: Maxim Kozlovsky; Larry Scheer; dl-Cougar<BR>
Subject: RE: bobcat linux unusable after fti<BR>
<BR>
<BR>
Once enough cougar systems became available and everyone moved to =
cougar<BR>
we stopped testing on bobcat linux. I don't want to spend time now =
fixing bobcat linux defects.<BR>
Use a cougar.<BR>
<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
_____________________________________________<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; From: &nbsp; Maxim =
Kozlovsky&nbsp;<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Sent:&nbsp;&nbsp; Thursday, =
April 03, 2008 4:51 PM<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; To:&nbsp;&nbsp;&nbsp;&nbsp; =
Larry Scheer; dl-Cougar<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Subject:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; RE: bobcat linux =
unusable after fti<BR>
<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; You can't be serious, can =
you? You mean you've known that it is broken for a month and did not fix =
it or at the very least did not file a bug?<BR>
<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; I've been using bobcat linux =
up until now without any problems.<BR>
<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
_____________________________________________<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; From: Larry Scheer<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Sent: Thursday, April 03, =
2008 5:46 PM<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; To: Maxim Kozlovsky; =
dl-Cougar<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Subject: RE: bobcat linux =
unusable after fti<BR>
<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Bobcat Linux has been =
unusable for a month or so. The best I could do was boot Linux only but =
the minute I try to start pm and the ONStor processes weirdness =
ensues.<BR>
<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
_____________________________________________<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; From: Maxim Kozlovsky<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Sent: Thursday, April 03, =
2008 5:42 PM<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; To: dl-Cougar<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Subject: bobcat linux =
unusable after fti<BR>
<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Hello,<BR>
<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; I had some misguided notion =
couple of days ago that I should upgrade my bobcat linux booting from =
NFS to the latest rootfs and configure it from scratch. It has become =
unusable after I've configured it through nfxsh. Could somebody please =
fix this problem and actually test the fix by upgrading 10.2.10.2 to the =
latest code? I'd like to have my bobcat back.<BR>
<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Max<BR>
<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C89675.9DAA2120--
