The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: will.senn@gmail.com (Will Senn)
Subject: [TUHS] Determining what was on a tape back in the day
Date: Sun, 19 Nov 2017 08:55:51 -0600	[thread overview]
Message-ID: <83A46968-F88E-4FE0-B7A0-012109EE33CC@gmail.com> (raw)
In-Reply-To: <20171119134109.59F3018C0F5@mercury.lcs.mit.edu>



Sent from my iPhone

On Nov 19, 2017, at 7:41 AM, Noel Chiappa <jnc at mercury.lcs.mit.edu> wrote:
>  https://www.ebay.com/itm/Digital-pdp-Programming-Card-8-Pages/142565890514
> 
> is useful;


Thanks, Noel,

The archive has the card:
https://archive.org/details/bitsavers_decpdp11PDul75_1582192

> 
> Well, you need to differentiate between DECtape and magtape - very different
> beasts.
> 
> DECtape on a PDP-11 _only_ supports 256 word (i.e. 512 byte) blocks, the same
> as most disks. (Floppies are an exception when it comes to disks - sort
> of. The hardware supports 128/256 byte sectors, but the usual driver - not in
> V6 or V7 - invisibly makes them look like 512-byte blocks.)

> Magtapes are complicated, and I don't remember all the details of how Unix
> handles them, but the _hardware_ is prepared to write very long 'blocks', and
> there are also separate 'file marks' which the hardware can write, and notice.
> 
> But a magtape written in 512-byte blocks, with no file marks, can be treated
> like a disk; that's what the V6 distribution tapes look like:

I think I understand- the bytes that we have on hand are not device faithful representations, but rather are failthful representations of what is presented to the OS. That is, back in the day, a tape would be stored in various formats as would disks, but unix would show these devices as streams of bytes, and those are the streams of bytes are what have been preserved. 

Some formats have header info, file lists, and such placed in predetermined locations, and some have different block sizes, file/tape marks, but no track, sector type or device specific info is retained? Does this sound reasonably accurate?

Will
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20171119/623f856e/attachment.html>


  parent reply	other threads:[~2017-11-19 14:55 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-19 13:41 Noel Chiappa
2017-11-19 14:55 ` Clem cole
2017-11-19 21:00   ` William Corcoran
2017-11-19 21:19     ` Ron Natalie
2017-11-19 22:00       ` Dave Horsfall
2017-11-19 22:38         ` Lyndon Nerenberg
2017-11-19 22:40         ` Ronald Natalie
2017-11-19 23:41           ` Dave Horsfall
2017-11-20  1:02             ` Ronald Natalie
2017-11-20  1:18               ` Dave Horsfall
2017-11-20 18:12                 ` Random832
2017-11-20 23:22                   ` Dave Horsfall
2017-11-20 23:35                     ` William Pechter
2017-11-21  0:01                     ` Ron Natalie
2017-11-20 19:02   ` Paul Winalski
2017-11-19 14:55 ` Will Senn [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-11-20 19:42 Noel Chiappa
2017-11-20 17:00 Noel Chiappa
2017-11-20 16:01 Noel Chiappa
2017-11-20 17:37 ` Will Senn
2017-11-19 20:46 Steve Simon
2017-11-19 18:45 Noel Chiappa
2017-11-19 17:49 Noel Chiappa
2017-11-19 18:35 ` Arthur Krewat
2017-11-18 19:23 Noel Chiappa
2017-11-18 21:32 ` Will Senn
2017-11-18 21:49   ` Warren Toomey
2017-11-18 18:34 Noel Chiappa
2017-11-18 18:37 ` Ronald Natalie
2017-11-18 18:40   ` Ronald Natalie
2017-11-18 21:51   ` Dave Horsfall
2017-11-18 21:07 ` Will Senn
2017-11-18 22:53   ` Clem Cole
2017-11-19  1:47     ` Will Senn
2017-11-18 16:39 Will Senn
2017-11-18 18:57 ` Clem Cole
2017-11-18 20:03   ` Don Hopkins
2017-11-18 22:37     ` Dave Horsfall
2017-11-18 23:16       ` Don Hopkins
2017-11-18 23:35         ` Arthur Krewat
2017-11-19  0:35           ` Steve Nickolas
2017-11-19  0:42             ` Don Hopkins
2017-11-19  1:04               ` Clem cole
2017-11-19 16:20                 ` Arthur Krewat
2017-11-20  2:33         ` Lawrence Stewart
2017-11-18 21:26   ` Will Senn
2017-11-18 22:39     ` Clem Cole

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83A46968-F88E-4FE0-B7A0-012109EE33CC@gmail.com \
    --to=will.senn@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).