Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!zaphod.mps.ohio-state.edu!caen!umich!terminator!pisa.citi.umich.edu!rees
From: rees@pisa.citi.umich.edu (Jim Rees)
Newsgroups: comp.sys.apollo
Subject: Re: using tar on nfs file system.
Message-ID: <523f42f3.1bc5b@pisa.citi.umich.edu>
Date: 18 Jun 91 15:46:51 GMT
References: <1991Jun17.195903.20887@cpsc.ucalgary.ca>
Sender: usenet@terminator.cc.umich.edu (usenet news)
Reply-To: rees@citi.umich.edu (Jim Rees)
Organization: University of Michigan IFS Project
Lines: 20

In article <1991Jun17.195903.20887@cpsc.ucalgary.ca>, fridman@aa.cpsc.ucalgary.ca (Robert Fridman) writes:
  
  	tar: ERROR!! Cannot archive foo.  It is of type nfs_dir.

Whoever did this to tar should be shot.  No wait, they should be forced to
use MS-DOS, then shot.  Whoever did this has absolutely no concept of what
Domain/OS is all about, and clearly doesn't understand the first thing about
typed file systems.  I can only hope that this was some contractor and not
an actual Apollo engineer.

But those of us who have been using Apollo systems for a while know that
tar has never worked.  It's sort of a joke, but it's too bad that it has to
be at the customer's expense.

You can get a working version of tar from several different places.  I
suggest either the gnu tar, or John Gilmore's PD tar, which is available by
ftp from pisa.citi.umich.edu.

The funny thing is that if they had just taken the Berkeley tar and compiled
it, instead of mucking with it, it would work just fine.