From: Jonathan Gray <jsg@jsg.id.au>
To: Warren Toomey <wkt@tuhs.org>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: Some old DECtapes from Dennis Ritchie
Date: Fri, 14 Jul 2023 15:31:43 +1000 [thread overview]
Message-ID: <ZLDdv+m6jvvGQ0L/@largo.jsg.id.au> (raw)
In-Reply-To: <ZLAs4uvHguU7uWdp@largo.jsg.id.au>
On Fri, Jul 14, 2023 at 02:57:06AM +1000, Jonathan Gray wrote:
> On Tue, Jul 11, 2023 at 10:44:33AM +1000, Warren Toomey via TUHS wrote:
> > All, way back when, Dennis sent me some DECtape images to look after. I've
> > put some of them in the Unix Archive (the s1 and s2 tapes) as they contained
> > Unix source code or binaries. The others I kept aside as they didn't contain
> > Unix code, or they were potentially sensitive.
> >
> > Anyway, Angelo Papenhoff asked for any old tapes from the Labs that might
> > contain fragments of B source code or B binaries. I passed the extra tapes
> > on to him, and he has found some very interesting nuggets from the time
> > period when B -> NB -> C.
> >
> > So, to help provide the context around Angelo's work, I've decided to put
> > all the tapes that Dennis gave me here:
> >
> > https://www.tuhs.org/Archive/Applications/Dennis_Tapes/
> >
> > Cheers, Warren
>
> Thank-you to all involved.
>
> Interesting that this has a version of
> "The UNIX Time-Sharing System" paper with timestamps close to the
> SOSP presentation.
>
> UnixEditionZero-Threshold_OCR.pdf 1971 draft
>
> Symposium on Operating System Principles, October 15-17 1973
> proceedings only have an abstract
The ACM online archive only has the abstract
https://dl.acm.org/doi/10.1145/800009.808045
but google books shows fragments of more in searches
https://books.google.com/books?id=TxNRAQAAIAAJ
>
> dmr_tapes/dmr2/tp/paper/p1 Nov 1973
> "about 20 installations have been put into service"
> (same number given in fourth edition manual also dated Nov 1973)
> "Files are named by sequences of eight or fewer characters"
>
> tuhs/Documentation/Papers/unix_cacm74.pdf July 1974
> "about 40 installations have been put into service"
> "Files are named by sequences of 14 or fewer characters"
>
> tuhs/Distributions/Research/Dennis_v6/v6doc.tar.gz unix/p1 Jun 1975
> "about 100 installations have been put into service"
DECUS: Proceedings of the Digital Equipment Computer Users Society
1977: Vol 3 Iss 5
https://archive.org/details/sim_digital-equipment-computer-users-society-transactions_1977_3_5
"about 250 installations have been put into service"
tuhs/Documentation/Papers/BSTJ/bstj57-6-1905.pdf July/Aug 1978
"over 600 installations have been put into service"
tuhs/Distributions/Research/Henry_Spencer_v7/v7.tar.gz
usr/doc/cacm Jan 1979
"over 600 installations have been put into service"
next prev parent reply other threads:[~2023-07-14 5:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-11 0:44 [TUHS] " Warren Toomey via TUHS
2023-07-11 6:24 ` [TUHS] " Lars Brinkhoff
2023-07-11 8:39 ` Sebastien F4GRX
2023-07-11 8:57 ` Lars Brinkhoff
2023-07-13 4:42 ` Lars Brinkhoff
2023-07-13 10:00 ` Sebastien F4GRX
2023-07-12 7:01 ` Jonathan Gray
2023-07-11 9:21 ` Henry Bent
2023-07-11 17:27 ` Angelo Papenhoff
2023-07-11 17:29 ` Angelo Papenhoff
2023-07-11 18:24 ` segaloco via TUHS
2023-07-11 23:54 ` KenUnix
2023-07-13 16:57 ` Jonathan Gray
2023-07-14 5:31 ` Jonathan Gray [this message]
2023-07-16 2:35 ` Phil Budne
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=ZLDdv+m6jvvGQ0L/@largo.jsg.id.au \
--to=jsg@jsg.id.au \
--cc=tuhs@tuhs.org \
--cc=wkt@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).