From: Warner Losh <imp@bsdimp.com>
To: Dennis Boone <drb@msu.edu>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Software Archaeology Challenge?
Date: Mon, 6 Apr 2020 19:59:57 -0600 [thread overview]
Message-ID: <CANCZdfpZ+CmrfZgdTVnfBJWSTiqGXh8WJgUCrF_Y3EAPqnC+AA@mail.gmail.com> (raw)
In-Reply-To: <20200406225949.88C792BB520@yagi.h-net.msu.edu>
[-- Attachment #1: Type: text/plain, Size: 1600 bytes --]
On Mon, Apr 6, 2020 at 5:00 PM Dennis Boone <drb@msu.edu> wrote:
> The tape was made by a PDP-11 system running RT-11. This manual may
> help a little:
>
>
> http://bitsavers.org/pdf/dec/pdp11/rt11/v5.6_Aug91/AA-PD6PA-TC_RT-11_Volume_and_File_Formats_Manual_Aug91.pdf
>
> TL;DR - This tape was written by just copying disk files to it, so the
> files which contain actual data are just images of the disk files.
>
> File 2 is a V6 image that's bootable like so
%pdp11
sim> set cpu 11/45
sim> att rk0 2.tape
sim> boot rk0
@rkunnix
login:
File 5 - this looks like a file system image.
>
It's the rest of the sources from the last disk. You can mount it like so
if you add a 'att rk1 5.tape' to the above
# mkdir /rk1
# /etc/mount /dev/rk1 /rk1
> File 8 - appears to be some sort of archiver output, but while the .ARC
> extension might lead you to suspect the old CP/M - MSDOS ARC program was
> responsible, that doesn't appear to be the case.
>
You'd think that from the name, but you can mount it also like the above.
With the 'att rk2 8.tape' and 'att rk3 11.tape'
# chdir /dev
# /etc/mknod rk2 b 0 2
# /etc/mknod rk3 b 0 3
# mkdir /rk2 /rk3
# /etc/mount /dev/rk2 /rk2
# /etc/mount /deev/rk3 /rk3
> File 11 - this is an older format tarball.
>
Nah, somebody else used the disk before for TAR, and then this was
overwritten with a unix filesystem.
What's weird is that this is a VENIX system, which should be V7 which
should have a different filesystem layout from V6. I'd think I wouldn't be
able to see some directories. I'll have to create a V7 system and mount it
there...
Warner
[-- Attachment #2: Type: text/html, Size: 2939 bytes --]
next prev parent reply other threads:[~2020-04-07 2:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-06 22:11 Warren Toomey
2020-04-06 22:48 ` Henry Bent
2020-04-06 22:59 ` Dennis Boone
2020-04-07 1:59 ` Warner Losh [this message]
2020-04-06 23:47 ` Warren Toomey
2020-04-07 0:04 ` Henry Bent
2020-04-07 0:18 ` Henry Bent
2020-04-07 0:59 ` Clem Cole
2020-04-07 2:03 ` Dave Horsfall
2020-04-07 2:40 ` Jason Stevens
2020-04-07 3:39 ` Warner Losh
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=CANCZdfpZ+CmrfZgdTVnfBJWSTiqGXh8WJgUCrF_Y3EAPqnC+AA@mail.gmail.com \
--to=imp@bsdimp.com \
--cc=drb@msu.edu \
--cc=tuhs@tuhs.org \
/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).