Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!decwrl!decvax!eagle_snax!gmcgary
From: gmcgary@eagle_snax.UUCP ( Sun ECD Software)
Newsgroups: comp.sources.d
Subject: Re: Wiping out /bin in OS upgrades
Message-ID: <271@eagle_snax.UUCP>
Date: 31 Mar 88 21:20:02 GMT
References: <1682@desint.UUCP> <1007@mcgill-vision.UUCP> <46626@sun.uucp> <1703@desint.UUCP> <10851@mimsy.UUCP>
Reply-To: gmcgary@eagle_snax.UUCP (Greg McGary - Sun ECD Software)
Organization: Sun Microsystems - East Coast Division
Lines: 26

Here's a simple procedure for preserving locally modified files across
upgrades/installations:

* As preparation, when a new installation is complete, create an empty
  file called /epoch, or whatever.  The mod-time of this file will be
  used later as a reference point.

* When it comes time to do another installation/upgrade,
  `find / -newer /epoch -print' will yield a list of files that have
  been added/changed since the last installation/upgrade.
  You may want to hand-edit this list of files to filter out the cruft.

* Use the list of files to create an archive with cpio(1) or tar(1)
  or whatever.

* Install/upgrade the new release.

* Load your archive of locally modified files on top of the new release.

* Touch /epoch for the next time around.

-- 
-- Greg McGary	
--		gmcgary@ecd.sun.com
--			{ucbvax,seismo,ihnp4,cbosgd}!sun!eagle_snax!gmcgary
--			    {decvax,ima,alliant,phoenix}!eagle_snax!gmcgary