Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!umich!terminator!pisa.ifs.umich.edu!rees
From: rees@pisa.ifs.umich.edu (Jim Rees)
Newsgroups: comp.sys.apollo
Subject: Re: WBAK to filename
Message-ID: <4e841df7.1bc5b@pisa.ifs.umich.edu>
Date: 10 Dec 90 17:35:45 GMT
References: <9012061511.AA00171@cc2.cc.umr.edu> <101020015@hpcvlx.cv.hp.com>
Sender: usenet@terminator.cc.umich.edu (usenet news)
Reply-To: rees@citi.umich.edu (Jim Rees)
Organization: University of Michigan IFS Project
Lines: 14

In article <101020015@hpcvlx.cv.hp.com>, tomg@hpcvlx.cv.hp.com (Thomas J. Gilg) writes:

  If you use tar, consider the -A option to capture Apollo specific file
  attributes.  As for which of tar/wbak is better, I've found wbak to be more
  solid than tar.

In sr10.3 they fixed the bug where tar didn't truncate pre-existing files on
extraction (this caused problems with the emacs sources).  But it's still
got the bug where it loses the file mode bits.  I haven't tried '-A'.

I use one of the public domain versions of tar (John Gilmore's, but the gnu
one might be better) with extra hacks to make it preserve file type for obj
and coff.  I've never been able to get a handle on how rbak/wbak works.
Besides, the format isn't portable.