AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20080522113144.2c7bfab2@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<deepak.veliath@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	BB375AF679D4A34E9CA8DFA650E2B04E0A1C22B2@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Thu, 22 May 2008 11:33:23 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Deepak Veliath" <deepak.veliath@onstor.com>
Cc: "Larry Scheer" <larry.scheer@onstor.com>
Subject: Re: system upgrade resets .profile
Message-ID: <20080522113323.06d5eb95@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E0A1C22B2@onstor-exch02.onstor.net>
References: <BB375AF679D4A34E9CA8DFA650E2B04E0A0F8FE1@onstor-exch02.onstor.net>
	<20080521173415.204fc8b3@ripper.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04E042F01A1@onstor-exch02.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04E0A1C22B2@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


There are a number of files that fall into this category, and mostly
developers just keep their private copies somewhere safe and re-add
them to their filer at the appropriate times.  Files like /etc/fstab,
/root/.profile, and so forth.  Since they really shouldn't ever be
modified by a customer, we don't have a facility for coddling them.  I
think there are one or two packages that monitor files for changes that
perhaps could be leveraged in some way, but I don't think it's worth
the effort.

Cheers,

a

On Thu, 22 May 2008 11:22:46 -0700 "Deepak Veliath"
<deepak.veliath@onstor.com> wrote:

> Is there a way to specify that a (config) file should be updated only
> if its not been modified by the admin?
> 
> u> It didn't happen on BSD because the legacy systems did not 
> u> install a .profile. With Linux and  Bash we are installing a 
> u> .profile in /root. If anyone had a .profile it was because 
> u> it was created manually. 
> u> 
> u> On BSD systems it was the .cshrc file that was overwritten 
> u> with every upgrade. Our current product versions do not 
> u> preserve the dot files in /root that it "knows" about.
> u> 
> u> We could add the dot files to the list of files not to 
> u> upgrade. We have a couple of mechanisms for doing that. 
> u> 
> u> 1. We can ignore upgrading them by adding them to the descr 
> u> files 2. We can add them to the list of config files that 
> u> are preserved and copied whenever an upgrade or system 
> u> config <whatever> command is run.
