Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 8/1/84; site rlgvax.UUCP
Path: utzoo!watmath!clyde!burl!mgnetp!ihnp4!houxm!houxz!vax135!cornell!uw-beaver!tektronix!hplabs!zehntel!dual!amd!decwrl!decvax!harpo!utah-cs!seismo!rlgvax!guy
From: guy@rlgvax.UUCP
Newsgroups: net.unix
Subject: Re: WANTED:SYS V tar to read Berkeley tar
Message-ID: <42@rlgvax.UUCP>
Date: Mon, 6-Aug-84 23:00:49 EDT
Article-I.D.: rlgvax.42
Posted: Mon Aug  6 23:00:49 1984
Date-Received: Fri, 10-Aug-84 02:07:33 EDT
References: <261@hudson.UUCP>, <2601@seismo.UUCP> <3800@brl-tgr.ARPA>
Organization: CCI Office Systems Group, Reston, VA
Lines: 12

Well, I'm not yet sure Berkeley's 4.2BSD "tar" is incompatible.  Berkeley
writes "tar" tape entries for directories, as well as files ("tar" should
have done that in the first place), but those entries merely cause "tar"s
not equipped to handle them to complain about being unable to create
"./src/foobar/include/" and continue reading in the non-directory entries.
The "-o" option in the Berkeley "tar" causes those entries not to be written.
I've sent "tar" files from 4.2BSD systems to System III systems (not tapes,
admittedly - the "straight" System III systems we have are little boxes with
no 9-track tape) and read them with no problem.  Let's not cry wolf.

	Guy Harris
	{seismo,ihnp4,allegra}!rlgvax!guy