Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site brl-tgr.ARPA
Path: utzoo!linus!philabs!cmcl2!seismo!brl-tgr!internet!Jeff Mogul <mogul@Shasta>
From: Jeff Mogul <mogul@Shasta>
Newsgroups: net.unix-wizards
Subject: Re: \"tar\" and non-8-bit byte machines
Message-ID: <5955@brl-tgr.ARPA>
Date: Tue, 20-Nov-84 14:36:29 EST
Article-I.D.: brl-tgr.5955
Posted: Tue Nov 20 14:36:29 1984
Date-Received: Thu, 22-Nov-84 06:28:38 EST
Sender: news@brl-tgr.ARPA
Organization: Ballistic Research Lab
Lines: 21


    The issue is that, in order for the VAX to read S-1 text files
    and vice versa, text files must be stored using a different
    representation than binary files.  There is no reliable way to
    determine whether a file should be "text" or "binary" when the
    tape is written, and no field in the "tar" header for recording
    this information even if the writer could reliably figure it out.

This is one of the things that make Unix hard to use in a heterogeneous
environment (lack of file type tags), but I think the way out of your
dilemma is to assume that files are text files.

How often, after all, are you going to exchange binary files between
the S-1 and a Vax?  Tar is a fair standard for exchanging text
files, but if you try to move an 8-bit binary file from the Vax to
the S-1, you'll probably have to massage it anyway.  It might be
better to convert binary files to text (e.g., a list of decimal numbers)
than to try to solve the problem in tar.

So, optimize for the dominant case (text files) and hope that
binary files stay rare.