Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!uakari.primate.wisc.edu!caen!umich!terminator!pisa.ifs.umich.edu!rees
From: rees@pisa.ifs.umich.edu (Jim Rees)
Newsgroups: comp.sys.apollo
Subject: Re: Tar on the Apollos (Was Re: emacs 18.55 on Apollo SR10.2.p)
Message-ID: <1990Aug21.204935.10896@terminator.cc.umich.edu>
Date: 21 Aug 90 20:49:35 GMT
References: <1990Aug16.072024@asterix.luftfahrt.uni-stuttgart.de> <ASHERMAN.90Aug20150244@dino.ulowell.edu>
Sender: usenet@terminator.cc.umich.edu (usenet news)
Reply-To: rees@citi.umich.edu (Jim Rees)
Organization: University of Michigan IFS Project
Lines: 15

In article <ASHERMAN.90Aug20150244@dino.ulowell.edu>,
asherman@dino.ulowell.edu (Aaron Sherman) writes:
  I have known for a while that Apollo does not think much of tar, and 
  have, therefore used Gnu tar. Since it ports smoothly with no mods, I would
  suggest this to anyone who needs to use tar heavily on the Apollos.

I second this.  I don't trust Apollo tar.  I'm still using John Gilmore's
public domain tar, which the gnu version is based on.

I have made the following mods, which I'll be happy to pass on to anyone who
wants them.  It should be easy to apply these to the gnu tar as well.

1.  Adjust the file type for coff and obj files on extract.
2.  Don't try to dump rec, mbx, or other bizarre file types.
3.  Use direct registry calls instead of getpw* and caching.