Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!linus!philabs!cmcl2!harvard!husc6!panda!genrad!decvax!bellcore!ulysses!mhuxr!mhuxn!ihnp4!houxm!hropus!ki4pv!tanner From: tanner@ki4pv.UUCP (Tanner Andrews) Newsgroups: net.unix,net.unix-wizards Subject: Re: Question about cpio vs. tar Message-ID: <6908@ki4pv.UUCP> Date: Mon, 19-May-86 10:49:18 EDT Article-I.D.: ki4pv.6908 Posted: Mon May 19 10:49:18 1986 Date-Received: Sat, 24-May-86 00:32:18 EDT References: <236@oucs.UUCP> <468@ncr-sd.UUCP> <355@imagen.UUCP>, <746@steinmetz.UUCP> Organization: CompuData South, DeLand Lines: 12 Xref: linus net.unix:7245 net.unix-wizards:15105 Assuming that you have a reasonable idea of the amount of data which may be placed on the disk, xenix (80286 sys3, sys5) will accept a "k" in the control keyword. This allows specificiation of the size of the output volume; you will then be prompted "tar: mount next volume" and may do the reasonable thing. This also works with using removable disks as a back-up medium. Better speed may be obtained by specifying a blocking factor which is an integral multiple of the cylinder size (or sub-multiple, if your "tar" doesn't malloc() its buffer). -- Tanner Andrews