Upgrading to 5.014

[Brian K. White]

----- Original Message ----- 
From: "Matthew Williams" <matthew.d.williams at gmail.com>
To: <filepro-list at lists.celestial.com>
Sent: Tuesday, January 11, 2005 2:04 PM
Subject: Re: Upgrading to 5.014


> What would be the correct syntax to extract the files?
> I have tried:
>
> # tar xvf develop.gz
> tar: blocksize = 20
> tar: directory checksum error
>
> If I try with the z flag I get "unknown option"
>
> # gtar zxvf develop.gz
> compress: stdin: not in compressed format
> # gtar xvf develop.gz
> gtar: Hmm, this doesn't look like a tar archive.
> gtar: Skipping to next file header...
> gtar: only read 8407 bytes from archive develop.gz
>
> I guess I need my hand held on this one.  I'm not so much a UNIX guy,
> I just got put on the job to do the upgrade.

I think your file got corrupted along the way, or never got downloaded right 
in the first place.

I bet "file develop.gz" doesn't say either "tar" or "compressed".

Download again and be more careful how you transfer it to the unix box.

when you get the file again, make sure if you use ftp to get it on the unix 
box, that you use the "bin" command in the ftp client before you do the 
"put"

then on unix run "file filename"
if it says compressed data then run "zcat filename |tar xvf -"
if it says gzip compressed data then run "gzcat filename |tar xvf -"
if it says tar archive then run "tar xvf filename"
Anything else and you got a corrupt file again.

As for doing the upgrade without potentially screwing up operations...

cd .../appl
copy -vrom fp fp.old
/tmp/finish   (the fp install script)

the installer should also save your old dir and make a new dir and if the 
stars are lined up right it'll keep your old edits and config file and 
everything should be fine, you might have some terminal emulation glitch at 
first if your old termcap file had been doctored but you can simply rename 
the new fp/termcap and copy the one from your old fp dir no problem.

If there is a problem, you can just rename the new fp dir and restore the 
old in a few seconds
mv fp fp.new ; copy -vrom fp.old fp
to put you back exacty where you were no problem.

The upgrade, even if the installer botches something, won't hurt your data.
If you did have to put the old dir back, then you can still work on the new 
dir while the compny runs on the old by you manually setting PFPROG, and 
possibly one or more of PFDIR, PFMENUS, PFCONFIG, PFGLOB in your environment 
that all contain fp.new in their values. After your happy you can swap the 
names of the live & new directories to put the new dir back into live use.
mv fp fp.x
mv fp.new fp

One reason I keep using commands that rename the fp directory instead of 
deleting or overwriting it's contents even when there already is an extra 
copy from  previuos step is that you can't delete or overwrite some of the 
files in the directory if they are currently in use, but you can rename the 
whole directory and put something else in it's place. This way as users 
naturally close & open programs eventually no one will be using any of the 
files in the old dir and you can delete it then.
If you do this while no one is using the system and you know that no cron 
job is going to run a report, then that's less of a concern.

Aside from that you want to keep a copy of your old fp dir at least for a 
while, and it's small enough that there is really no pressing need to ever 
get rid of it.

Brian K. White  --  brian at aljex.com  --  http://www.aljex.com/bkw/
+++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
filePro BBx  Linux SCO  Prosper/FACTS AutoCAD  #callahans Satriani