The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: norman@oclsc.org (Norman Wilson)
Subject: [TUHS] Work I've done with a PDP-11 simulator
Date: Sun, 11 May 2014 19:13:29 -0400 (EDT)	[thread overview]
Message-ID: <1399850019.15503.for-standards-violators@oclsc.org> (raw)

  The web page mentions files-11 which is ODS-1.

Technically (it is all coming back to me now):

FILES-11 is a family of file systems that started in RSX-11
(or perhaps before but that's the oldest instance I know).

ODS-1 is really FILES-11 ODS-1; ODS is `on-disk [something].'

RSX-11 used ODS-1.  VMS used ODS-2.  I'm not sure of all
the differences offhand, but they were substantial enough
that we ended up writing two different programs to fetch
files to UNIX from RSX and VMS volumes (we had the latter
to deal with too).  Certainly the directory entries were
different between the two: ODS-1 used RADIX-50-encoded
file names with at most six characters plus an at-most-three-
character `extension' (a term which newbies sometimes
improperly import into UNIX as well); I forget the exact
filename rules in VMS, but filenames certainly could be
longer than six characters.

I've found the early-1980s programs I remembered.  There
were two, getrsx.c and getvms.c; two programs, one for
each file-system format.  They are surely full of ancient
sloppiness that won't compile or won't work right under
a modern C compiler, and they make assumptions about byte
order.  I'll spend some time in the next few days going over
them and see if I can quickly get something workable.

A footnote as to their origin: in the world where we wrote
these programs, we had not only multiple systems, but
shared disk drives.  The disk drives themselves were
dual-ported; the controllers we used could connect to
multiple hosts as well.  Each system had its own dedicated
disk drives, but the UNIX systems could also see the drives
belonging to the RSX and VMS systems; hence the file-fetching
programs, since this was well before the sort of networking
we take for granted these days.

On the other hand, we had several UNIX systems which spoke
uucp to one another, and that was occasionally used for
large file transfers.  To speed that up, I taught uucico
a new protocol, whereby control information still went over
a serial line, but data blocks were transferred over a
chunk of raw shared disk (with appropriate locks, of course).

It was a simpler world back then, but that made it a lot more fun.

Norman Wilson
Toronto ON



             reply	other threads:[~2014-05-11 23:13 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-11 23:13 Norman Wilson [this message]
2014-05-12  5:29 ` John Cowan
  -- strict thread matches above, loose matches on Subject: below --
2014-05-12 19:10 Noel Chiappa
2014-05-12 20:59 ` SPC
2014-05-12 17:06 Noel Chiappa
2014-05-12 17:20 ` SPC
2014-05-12 19:50 ` John Cowan
2014-05-12 14:49 Noel Chiappa
2014-05-11 16:16 Norman Wilson
2014-05-11 16:45 ` John Cowan
2014-05-11 22:19   ` pechter
2014-05-11  3:26 Noel Chiappa
2014-05-11  3:13 Noel Chiappa
2014-05-11  4:20 ` John Cowan
2014-05-11  2:06 Noel Chiappa
2014-05-11  2:31 ` Gregg Levine
2014-05-11  2:34   ` Gregg Levine
2014-05-11 17:21 ` Clem Cole
2014-05-11 17:24   ` Clem Cole
2014-05-11 18:50   ` Ronald Natalie
2014-05-11  0:51 Noel Chiappa
2014-05-11  0:57 ` Larry McVoy
2014-05-11  1:27   ` John Cowan
2014-05-11  1:58     ` Larry McVoy
2014-05-11  2:40       ` John Cowan
2014-05-05 15:32 Noel Chiappa
2014-05-04 23:54 Noel Chiappa
2014-05-05  1:53 ` John Cowan
2014-05-05  8:10   ` SPC
2014-04-30  2:19 Noel Chiappa
2014-05-03 22:14 ` SPC
2014-05-03 22:20   ` Gregg Levine
2014-05-03 22:22     ` Larry McVoy
2014-05-05 13:50 ` Kurt H Maier

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=1399850019.15503.for-standards-violators@oclsc.org \
    --to=norman@oclsc.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).