Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!constellation!news.ysu.edu!malgudi.oar.net!warlock.win.net!warlock.win.net!not-for-mail From: bugs@news.win.net (Mark Hittinger) Newsgroups: comp.os.386bsd.questions Subject: Re: Upgrading to latest SNAP Date: 18 Feb 1995 16:40:07 -0500 Organization: Win.Net Communications, Inc. Lines: 44 Message-ID: <3i5pfn$bqo@warlock.win.net> References: <3hl7kb$ntj@earth.usa.net> <D3xwFK.4Lt@pencotts.demon.co.uk> NNTP-Posting-Host: warlock.win.net X-Newsreader: NN version 6.5.0 #4 (NOV) I have used this technique for each snap since the first one. I've almost got a set of shell scripts ready to do this. Download the snap. Use the "tar -df" command to produce a list of what has changed. You want to get the following files: 1. Size differs 2. Data differs 3. Does not exist Extract those files into a tree. Delete the files which you do not want changed (/etc stuff usually). I have patches for perl and for uncompress ect which I don't want mangled. Beware if you use "secrdist" you must do that last. Make a new tar archive of the updated files. shutdown to single user copy shell and tar to /tmp and exec the /tmp shell you will probably want to change the "noschg" flag on some files like init, rcp, login, ect you want to mv /sbin/init to /sbin/init.b4 run the /tmp tar and extract everything reboot This is fraught with peril if you don't know how to dig out of a mistake. This works fairly well for my "semi-production" environment. I got tripped up on the first snapshot with the routed changes but since then I've not had any trouble. Cheers! Mark Hittinger bugs@win.net