The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Angelo Papenhoff <>
Subject: Re: [TUHS] A Couple of New Unix Artifacts
Date: Tue, 17 Sep 2019 12:45:18 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 17/09/19, Warren Toomey wrote:
> I fear we're drifting a bit here and the S/N ratio is dropping a bit w.r.t
> the actual history of Unix. Please no more on the relative merits of
> version control systems or alternative text processing systems.
> So I'll try to distract you by saying this. I'm sitting on two artifacts
> that have recently been given to me:
>  + by two large organisations
>  + of great significance to Unix history
>  + who want me to keep "mum" about them
>  + as they are going to make announcements about them soon *
> and I am going slowly crazy as I wait for them to be offically released.
> Now you have a new topic to talk about :-)

That sounds exciting!

I wish we had more stuff of the v0-v4 era, but I don't know how
likely that is to even still exist.
Also the things that were documented in the manual but weren't in the
distribution...old troff is something that comes to mind. We still have
the source filenames in deleted directory entries in the v6 distribution.

  parent reply	other threads:[~2019-09-17 10:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-17  9:54 Warren Toomey
2019-09-17  9:58 ` SPC
2019-09-17 10:45 ` Angelo Papenhoff [this message]
2019-09-17 23:12 ` Dave Horsfall
2019-09-17 23:25   ` Arthur Krewat
2019-09-18  0:47     ` Adam Thornton
2019-09-18  0:54       ` Arthur Krewat
2019-09-18  1:03         ` Adam Thornton
2019-09-18  9:06     ` Wesley Parish
2019-09-18 14:40       ` Larry McVoy
2019-09-18 16:33 ` Seth Morabito
2019-09-18 21:17   ` A. P. Garcia
2019-09-18 23:05 ` Sergio Aguayo via TUHS
2019-09-18 23:25   ` Warren Toomey
2019-09-19  0:42     ` Nigel Williams
2019-09-19  1:35       ` Gregg Levine
2019-09-19  5:06         ` Lars Brinkhoff

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:

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

  git send-email \ \ \ \

* 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).