Received: (from major@localhost)
	by minnie.cs.adfa.oz.au (8.8.5/8.8.5) id RAA20686
	for pups-liszt; Wed, 25 Mar 1998 17:00:29 +1100 (EST)
X-Authentication-Warning: minnie.cs.adfa.oz.au: major set sender to owner-pups@minnie.cs.adfa.oz.au using -f
Received: from psychvax.psych.usyd.edu.au (psychvax.psych.usyd.edu.au [129.78.83.1])
	by minnie.cs.adfa.oz.au (8.8.5/8.8.5) with ESMTP id RAA20681
	for <pups@minnie.cs.adfa.oz.au>; Wed, 25 Mar 1998 17:00:26 +1100 (EST)
Received: (from johnh@localhost)
	by psychvax.psych.usyd.edu.au (8.8.8/8.8.8) id RAA02807
	for pups@minnie.cs.adfa.oz.au; Wed, 25 Mar 1998 17:00:21 +1100
Date: Wed, 25 Mar 1998 17:00:21 +1100
From: John Holden <johnh@psychvax.psych.usyd.edu.au>
Message-Id: <199803250600.RAA02807@psychvax.psych.usyd.edu.au>
To: pups@minnie.cs.adfa.oz.au
Subject: Re: What's magtape good for anyway?
Sender: owner-pups@minnie.cs.adfa.oz.au
Precedence: bulk


There were several tape handling programs that were standand from edition 5
onwards, including tap, tp, dtp, itp, tar and cpio. The only major tape standard
around at the time (other than IBM) was ANSI, and several programs (not from
Bell) were available to handle these. The ANSI tape structure was very
inefficient with tape usage, since it used small record sizes and lots
of tape marks. TAR did a better job (for Unix) and only lacked labels
to name the tape.

Putting tape filesystem handling into the kernel was definately against the
original 'small is beautiful' philosophy. In any case, tape handling was
very easy via the raw interface.

As a side issue, Plan 9 has the ability to mount a tape as part of the
namespace and only reads the file contents if the file is opened.

