X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C8BBAB.4DF17790@onstor-exch02.onstor.net>; Wed, 21 May 2008 18:29:40 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8BBAB.4DF17790"
References: <BB375AF679D4A34E9CA8DFA650E2B04E0A0F8FE1@onstor-exch02.onstor.net> <20080521173415.204fc8b3@ripper.onstor.net>
Content-class: urn:content-classes:message
Subject: RE: system upgrade resets .profile
Date: Wed, 21 May 2008 18:29:40 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E042F01A1@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: system upgrade resets .profile
Thread-Index: Aci7o5DIZXTKLA66SZG971b2A6yL3QABsjhr
From: "Larry Scheer" <larry.scheer@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>,
	"Deepak Veliath" <deepak.veliath@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8BBAB.4DF17790
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

It didn't happen on BSD because the legacy systems did not install a =
.profile. With Linux and  Bash we are installing a .profile in /root. If =
anyone had a .profile it was because it was created manually.=20

On BSD systems it was the .cshrc file that was overwritten with every =
upgrade. Our current product versions do not preserve the dot files in =
/root that it "knows" about.

We could add the dot files to the list of files not to upgrade. We have =
a couple of mechanisms for doing that.=20

1. We can ignore upgrading them by adding them to the descr files
2. We can add them to the list of config files that are preserved and =
copied whenever an upgrade or system config <whatever> command is run.


-----Original Message-----
From: Andy Sharp
Sent: Wed 5/21/2008 5:34 PM
To: Deepak Veliath
Cc: Larry Scheer
Subject: Re: system upgrade resets .profile
=20
On Wed, 21 May 2008 15:20:07 -0700 "Deepak Veliath"
<deepak.veliath@onstor.com> wrote:

> Hello Andy,
> I notice that a system upgrade on Cougar resets/overwrites .profile.
> This doesn't happen on BSD.  Is this on purpose?
>=20
> veliath

I think it's by accident.  I think it's only suppose to write it
during flash_install.  Larry?




------_=_NextPart_001_01C8BBAB.4DF17790
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: system upgrade resets .profile</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>It didn't happen on BSD because the legacy systems did =
not install a .profile. With Linux and&nbsp; Bash we are installing a =
.profile in /root. If anyone had a .profile it was because it was =
created manually.<BR>
<BR>
On BSD systems it was the .cshrc file that was overwritten with every =
upgrade. Our current product versions do not preserve the dot files in =
/root that it &quot;knows&quot; about.<BR>
<BR>
We could add the dot files to the list of files not to upgrade. We have =
a couple of mechanisms for doing that.<BR>
<BR>
1. We can ignore upgrading them by adding them to the descr files<BR>
2. We can add them to the list of config files that are preserved and =
copied whenever an upgrade or system config &lt;whatever&gt; command is =
run.<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: Andy Sharp<BR>
Sent: Wed 5/21/2008 5:34 PM<BR>
To: Deepak Veliath<BR>
Cc: Larry Scheer<BR>
Subject: Re: system upgrade resets .profile<BR>
<BR>
On Wed, 21 May 2008 15:20:07 -0700 &quot;Deepak Veliath&quot;<BR>
&lt;deepak.veliath@onstor.com&gt; wrote:<BR>
<BR>
&gt; Hello Andy,<BR>
&gt; I notice that a system upgrade on Cougar resets/overwrites =
.profile.<BR>
&gt; This doesn't happen on BSD.&nbsp; Is this on purpose?<BR>
&gt;<BR>
&gt; veliath<BR>
<BR>
I think it's by accident.&nbsp; I think it's only suppose to write =
it<BR>
during flash_install.&nbsp; Larry?<BR>
<BR>
<BR>
<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C8BBAB.4DF17790--
