Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!maverick.ksu.ksu.edu!hoss!fergvax!vandevek
From: vandevek@fergvax.unl.edu (James M. VandeVegt)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: WANTED:  TAR UNCOMPRESSOR FOR MS-DOS
Message-ID: <1991Feb15.142501.7632@hoss.unl.edu>
Date: 15 Feb 91 14:25:01 GMT
References: <1991Feb12.043510.6138@usenet.ins.cwru.edu> <1991Feb13.060554.4933@hoss.unl.edu> <444@newmedia.UUCP>
Sender: news@hoss.unl.edu (Network News Administer)
Organization: Comp Sci and Engr, Univ. of Nebr.
Lines: 23

In article <444@newmedia.UUCP> jim@newmedia.UUCP (Jim Beveridge) writes:
>In article <1991Feb13.060554.4933@hoss.unl.edu>, vandevek@fergvax.unl.edu (James M. VandeVegt) writes:
>> {$F=1}      {Turn flame mode on}
>> Tar is NOT a compressor.  It mearly places numerous
>> files into one file so that they can be stored together
>> for ease of later finding them and making sense out of them.
>> {$F=0}
>
>{$F=maybe}
>Well, actually, if you have one of the new versions of tar that
>can automatically call compress, then it *looks* like it does
>compression...   (I know, it really calls compress, but try
>explaining fork(), wait(), system(), etc. to a new user.)
>{$F=disable}
>
Thank you for this valuable information, I will look for a
unix version of tar that does this.


| James M. VandeVegt             |  University of Nebraska           |
| vandevek@fergvax.unl.edu       |  Computer Science and Engineering |
----------------------------------------------------------------------
|                  Insert standard disclaimer here.                  |