X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C88264.2CAE2CF2@onstor-exch02.onstor.net>; Sun, 9 Mar 2008 21:06:53 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C88264.2CAE2CF2"
References: <BB375AF679D4A34E9CA8DFA650E2B04E0149B663@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E08C0F698@onstor-exch02.onstor.net>
Content-class: urn:content-classes:message
Subject: RE: change #28253
Date: Sun, 9 Mar 2008 21:05:24 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E0149B664@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: change #28253
Thread-Index: AciCTNgV6bAeFb11T7GWN2EJiA4aIQAD2cIQAAHuCvY=
From: "Rendell Fong" <rendell.fong@onstor.com>
To: "Kumar Vakacharla (HCL)" <kumarv@onstor.com>
Cc: "Andy Sharp" <andy.sharp@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C88264.2CAE2CF2
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Ok, just checking to make sure nothing got broken.

Rendell




-----Original Message-----
From: Kumar Vakacharla (HCL)
Sent: Sun 3/9/2008 8:49 PM
To: Rendell Fong
Cc: Andy Sharp
Subject: RE: change #28253
=20
Hi,

=20

Yes, I have tested it on Bobcat and works fine.=20

I have overwritten your change as per Andy's comments.

=20

Coming to the "-e" option in echo command please find my observations =
below:

=20

=B7         I even observed that newline(\n) itself is not available in =
echo of the openBSD.=20

e.g:

eng21# echo "hi\nkumar"

hi\nkumar=20

eng21#

=20

=B7         During CLI call "system get all " we execute a system =
command which invokes support.sh with necessary arguments.=20

As system function spawns a new shell "sh" and runs this script, the new =
shell (sh) will overwrite the echo which comes as part of

openbsd's C shell.=20

=20

=B7         I think in "sh", backslash character support is enabled by =
default for echo command irrespective of "-e" option. If we want to =
turnoff this feature we have to provide "-E" option.=20

e.g:

In BSD:

eng21# echo -e "hi\nkumar"

-e hi\nkumar

eng21#sh <------------------- switch to shell "sh"=20

# echo "hello\nkumar"

hello

kumar

# echo -e "hello\nkumar"

hello

kumar

# echo -E "hello\nkumar"

hello\nkumar

=20

=B7         In bash used by linux, has this feature disabled by default =
and we need to specify "-e" to turn it on explicitly. =20

E.g:

In Linux:=20

=20

g11r204:/ # echo "hello\nkumar"

hello\nkumar

g11r204:/ # echo -e "hello\nkumar"

hello

kumar

g11r204:/ # echo -E "hello\nkumar"

hello\nkumar

g11r204:/ #

=20

 Please correct me if my understanding is wrong.=20

=20

=20

Thanks,

Kumar.

=20

=20

-----Original Message-----
From: Rendell Fong=20
Sent: Sunday, March 09, 2008 6:20 PM
To: Kumar Vakacharla (HCL)
Cc: Andy Sharp
Subject: change #28253

=20

=20

Hi,

=20

The submittal of support.sh in change #28253 was not resolved properly.  =
The echo option that you added already existed in the previous version.  =
Also, have you tested this change on Bobcat?  OpenBSD doesn't have an =
echo -e option as far as I can tell.  The previous version checked for =
this case.

=20

Thanks,

Rendell=20



------_=_NextPart_001_01C88264.2CAE2CF2
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: change #28253</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>Ok, just checking to make sure nothing got broken.<BR>
<BR>
Rendell<BR>
<BR>
<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: Kumar Vakacharla (HCL)<BR>
Sent: Sun 3/9/2008 8:49 PM<BR>
To: Rendell Fong<BR>
Cc: Andy Sharp<BR>
Subject: RE: change #28253<BR>
<BR>
Hi,<BR>
<BR>
<BR>
<BR>
Yes, I have tested it on Bobcat and works fine.<BR>
<BR>
I have overwritten your change as per Andy's comments.<BR>
<BR>
<BR>
<BR>
Coming to the &quot;-e&quot; option in echo command please find my =
observations below:<BR>
<BR>
<BR>
<BR>
=B7&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; I even observed that =
newline(\n) itself is not available in echo of the openBSD.<BR>
<BR>
e.g:<BR>
<BR>
eng21# echo &quot;hi\nkumar&quot;<BR>
<BR>
hi\nkumar<BR>
<BR>
eng21#<BR>
<BR>
<BR>
<BR>
=B7&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; During CLI call =
&quot;system get all &quot; we execute a system command which invokes =
support.sh with necessary arguments.<BR>
<BR>
As system function spawns a new shell &quot;sh&quot; and runs this =
script, the new shell (sh) will overwrite the echo which comes as part =
of<BR>
<BR>
openbsd's C shell.<BR>
<BR>
<BR>
<BR>
=B7&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; I think in =
&quot;sh&quot;, backslash character support is enabled by default for =
echo command irrespective of &quot;-e&quot; option. If we want to =
turnoff this feature we have to provide &quot;-E&quot; option.<BR>
<BR>
e.g:<BR>
<BR>
In BSD:<BR>
<BR>
eng21# echo -e &quot;hi\nkumar&quot;<BR>
<BR>
-e hi\nkumar<BR>
<BR>
eng21#sh &lt;------------------- switch to shell &quot;sh&quot;<BR>
<BR>
# echo &quot;hello\nkumar&quot;<BR>
<BR>
hello<BR>
<BR>
kumar<BR>
<BR>
# echo -e &quot;hello\nkumar&quot;<BR>
<BR>
hello<BR>
<BR>
kumar<BR>
<BR>
# echo -E &quot;hello\nkumar&quot;<BR>
<BR>
hello\nkumar<BR>
<BR>
<BR>
<BR>
=B7&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; In bash used by =
linux, has this feature disabled by default and we need to specify =
&quot;-e&quot; to turn it on explicitly.&nbsp;<BR>
<BR>
E.g:<BR>
<BR>
In Linux:<BR>
<BR>
<BR>
<BR>
g11r204:/ # echo &quot;hello\nkumar&quot;<BR>
<BR>
hello\nkumar<BR>
<BR>
g11r204:/ # echo -e &quot;hello\nkumar&quot;<BR>
<BR>
hello<BR>
<BR>
kumar<BR>
<BR>
g11r204:/ # echo -E &quot;hello\nkumar&quot;<BR>
<BR>
hello\nkumar<BR>
<BR>
g11r204:/ #<BR>
<BR>
<BR>
<BR>
&nbsp;Please correct me if my understanding is wrong.<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
Thanks,<BR>
<BR>
Kumar.<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: Rendell Fong<BR>
Sent: Sunday, March 09, 2008 6:20 PM<BR>
To: Kumar Vakacharla (HCL)<BR>
Cc: Andy Sharp<BR>
Subject: change #28253<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
Hi,<BR>
<BR>
<BR>
<BR>
The submittal of support.sh in change #28253 was not resolved =
properly.&nbsp; The echo option that you added already existed in the =
previous version.&nbsp; Also, have you tested this change on =
Bobcat?&nbsp; OpenBSD doesn't have an echo -e option as far as I can =
tell.&nbsp; The previous version checked for this case.<BR>
<BR>
<BR>
<BR>
Thanks,<BR>
<BR>
Rendell<BR>
<BR>
<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C88264.2CAE2CF2--
