Received: (from major@localhost)
	by minnie.cs.adfa.oz.au (8.8.5/8.8.5) id BAA21915
	for pups-liszt; Thu, 26 Mar 1998 01:33:52 +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 europe.std.com (europe.std.com [199.172.62.20])
	by minnie.cs.adfa.oz.au (8.8.5/8.8.5) with ESMTP id BAA21910
	for <pups@minnie.cs.adfa.oz.au>; Thu, 26 Mar 1998 01:33:47 +1100 (EST)
Received: from world.std.com by europe.std.com (8.7.6/BZS-8-1.0)
	id JAA15971; Wed, 25 Mar 1998 09:33:42 -0500 (EST)
Received: by world.std.com (TheWorld/Spike-2.0)
	id AA22737; Wed, 25 Mar 1998 09:33:41 -0500
Date: Wed, 25 Mar 1998 09:33:41 -0500
From: allisonp@world.std.com (Allison J Parent)
Message-Id: <199803251433.AA22737@world.std.com>
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 are certain areas of Unix that don't seem quite "done" to me. 
<Printing comes to mind (compare Unix benign neglect with Windows'
<universal printer driver).  

Most of magtapes short commings under unix are common across most OSs
and are assignable to the characterisitcs of the medium.  Mag tape has
several things that make it difficult, one is old (late 60s and through
the 70s) drives had a difficult time starting and stopping without 
breaking tape or resorting to complex(then standards) controllers.  This 
lead to things like large interrecord gaps (start, speed up read, stop,
backspace records, stop, read) due to the inerta of starting and stoping 
the reels.  Also fixed record sizes were used to make blocks about the 
same length so blocks and marks could be differentiated using simple 
timers.

Magtape was for the longest time the only portable media, which lead to 
the ansi/EBCDIC problems (Evryone else and IBM/HP).  It was generally 
used for archival storage making file organized access excess overhead.  
While often used as block oriented, many systems used it more as a stream 
device where the high volume storage (relative to the disks of the time) 
capability was available.

When processing was done on early system usually two or three drives were 
involved as one of two were for reading  and the third was writing results
usually due to memory size limitations of the time compared to the amount 
of data.  Alot of magtapes lore is a result of historical use.

FYI the idea of tar files had spilled over to CP/M (8080, z80) systems 
back in the 80s for distribution sets.  It was done usually by creating
an archive set of compressed files (.arc, .ark, .lbr). to get the most 
out of limited space of floppies (under 300k) of the time and to keep 
programs set and sources together.


Allison


