Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!spool.mu.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!rpi!masscomp!peora!tarpit!bilver!bill
From: bill@bilver.uucp (Bill Vermillion)
Newsgroups: comp.unix.xenix.misc
Subject: Re: backup program for xenix?
Message-ID: <1991Feb20.145008.6304@bilver.uucp>
Date: 20 Feb 91 14:50:08 GMT
References: <1991Feb17.065756.14535@nntp-server.caltech.edu> <1991Feb17.222611.29265@bilver.uucp> <1991Feb19.154228.6510@robobar.co.uk>
Organization: W. J. Vermillion - Winter Park, FL
Lines: 23

In article <1991Feb19.154228.6510@robobar.co.uk> ronald@robobar.co.uk (Ronald S H Khoo) writes:
>bill@bilver.uucp (Bill Vermillion) writes:
 
>> As to floppy errors, use good quality floppies, and backup often.
>> You could also re-read the floppies to make sure they were okay.
 
>But don't re-read them using tar tv2 because that *seeks* and thus
>does not re-read all the data.  Do tar tvf - < /dev/install (or whatever)
>instead.
 
 Absolutely.  There was a program called cktar on the net a few months ago.
 It gets the names from the tar device looks in the directory for a
 matching name, and then does a byte by byte compare.

It also is supposed to report for problems  matching UID's, GID's, and time
of modification difference, and will give a position in the file where the
comparison failed.  I don't know if those work because I run the check
after backing up so none of those have changed.


-- 
Bill Vermillion - UUCP: uunet!tarpit!bilver!bill
                      : bill@bilver.UUCP