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: Sat, 18 Nov 2017 15:07:35 -0600	[thread overview]
Message-ID: <367c50cf-8bee-e050-1c0c-0bd960621f37@gmail.com> (raw)
In-Reply-To: <20171118183451.CF48218C0F0@mercury.lcs.mit.edu>

On 11/18/17 12:34 PM, Noel Chiappa wrote:
> If you look here:
>
>    http://mercury.lcs.mit.edu/~jnc/tech/V6Unix.html#dumpf
>
> Try downloading it and compiling it - if it doesn't work, please let me know;
> it'd be worth fixing it so it does work on Linux.
Works fine. Thanks.
> The 0th block does seem to contain some PDP-11 binary - a bootstrap of some
> sort. I'll look in more detail in a bit.
Cool. I don't quite no how to investigate this other than to pore 
through the pdp11/40 instruction manual.
>  From what I can see, it's probably a tp-format tape: the 1st block contains
> some filenames which I can see in an ASCII dump of it:
>
>    speakez/sbrk.s
> ...
Well lookit that. I see it now, too :)
>      > v7 and look at its content using tm or tp, but then I realized that I
>      > didn't have a device set up for TU56
>
> You don't need to mount it on DECTape drive - it's just blocks. Mount it as
> an RK05 image, or a magtape, or whatever.
I thought disk (RK05) and tape (magtape) blocks were different...

Thanks,
Will


-- 
GPG Fingerprint: 68F4 B3BD 1730 555A 4462  7D45 3EAA 5B6D A982 BAAF



  parent reply	other threads:[~2017-11-18 21:07 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2017-11-18 22:53   ` Clem Cole
2017-11-19  1:47     ` Will Senn
  -- 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-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
2017-11-18 19:23 Noel Chiappa
2017-11-18 21:32 ` Will Senn
2017-11-18 21:49   ` Warren Toomey
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=367c50cf-8bee-e050-1c0c-0bd960621f37@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).