Received: (from major@localhost)
	by minnie.cs.adfa.oz.au (8.8.5/8.8.5) id PAA16670
	for pups-liszt; Tue, 24 Mar 1998 15:59:01 +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 alph02.triumf.ca (alph02.Triumf.CA [142.90.114.18])
	by minnie.cs.adfa.oz.au (8.8.5/8.8.5) with SMTP id PAA16665
	for <pups@minnie.CS.adfa.OZ.AU>; Tue, 24 Mar 1998 15:58:52 +1100 (EST)
Received: by alph02.triumf.ca; id AA14216; Mon, 23 Mar 1998 20:58:45 -0800
From: Tim Shoppa <shoppa@alph02.triumf.ca>
Message-Id: <9803240458.AA14216@alph02.triumf.ca>
Subject: Re: What's magtape good for anyway?
To: edgee@cyberpass.net
Date: Mon, 23 Mar 1998 20:58:44 -0800 (PST)
Cc: pups@minnie.cs.adfa.oz.au
In-Reply-To: <199803240249.VAA27961@renoir.op.net> from "Ed G." at Mar 23, 98 09:49:02 pm
X-Mailer: ELM [version 2.4 PL22]
Content-Type: text
Sender: owner-pups@minnie.cs.adfa.oz.au
Precedence: bulk

> To me (or maybe I just don't know what I'm talking about) it seems
> like magtape has a number of deficiencies:
> 
> No filenames or directory structure:  just an ordered series of 
> bytes.  Which would seem to imply that people must've used tar *a lot*
> to get these services.  True?

Most (non-Unix) minicomputer OS's had built-in support for
ANSI labeled files, which do have filenames (and header bytes to
specify record sizes and number of records).  Folks who used Unix
either made their own labeled tape facility (e.g. Ultrix and
OSF/1 "ltf") or just used "dd" and a lot of hard work.

The lack of a record structure that is built-in to the Unix filesystem
really makes things like tape transfers quite irritating.  The rest of
the world isn't always just a stream of bytes!

Tim. (shoppa@triumf.ca)

