The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] Questions regarding early Unix contributors
Date: Fri, 25 Sep 2015 08:04:58 -0400	[thread overview]
Message-ID: <CAC20D2OPd_+wTebXbeu17phaM=rDMkp+qKOUkqfkGbqssPK7ng@mail.gmail.com> (raw)
In-Reply-To: <alpine.NEB.2.11.1509241333120.27255@t1.m.reedmedia.net>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1124 bytes --]

On Thu, Sep 24, 2015 at 3:04 PM, Jeremy C. Reed <reed at reedmedia.net> wrote:

> But I cannot find 4.0 in Diomidis's git repo. I also don't have the
> original SCCS data from the early fsck, probably because it got moved
> and extended in different location.
>

​FYI:  "Early" fsck was developed before SCCS and PWB 1.0.   Version
control was what Ted has on his disk at the time.   At some point, I would
have expected that he put it under control @ Summit and wnj is likely to
have done the same at UCB.​  What is in the BSD repository is about 3-4
years into development.

As I said, Ted taught us all to use DOS-11 backup to make an image of his
RK05 to small of reel 9-track tape [800 bpi IIRC].  As I said, at one point
I had a couple of those tapes.  I looked for the box of them from CMU but I
free I may have disposed of them when I lost access to an 800 bpi drive [I
now have one, although it has an issue loading tapes I need to fix].

Clem
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20150925/2cb5b900/attachment.html>


  parent reply	other threads:[~2015-09-25 12:04 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-24 14:08 Clem Cole
2015-09-24 15:20 ` Mary Ann Horton
2015-09-24 17:08   ` Jeremy C. Reed
2015-09-24 17:28   ` Clem Cole
2015-09-26  2:37     ` Dave Horsfall
2015-09-26 23:22       ` Clement T. Cole
2015-09-27  6:52     ` Armando Stettner
2015-09-27 17:31       ` Clem Cole
2015-09-28 14:59       ` Dave Horsfall
2015-09-28 16:55         ` scj
2015-09-28 23:23           ` Greg 'groggy' Lehey
2015-10-01  2:09             ` Dave Horsfall
2015-10-01  3:52               ` Greg 'groggy' Lehey
2015-10-01  4:51                 ` Dave Horsfall
2015-09-29  6:57           ` arnold
2015-09-24 19:04 ` Jeremy C. Reed
2015-09-24 20:13   ` Clem Cole
2015-09-24 20:16     ` Clem Cole
2015-09-25  8:04   ` Diomidis Spinellis
2015-09-25 12:04   ` Clem Cole [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-10-07 13:26 Nelson H. F. Beebe
2015-10-02 18:00 Nelson H. F. Beebe
2015-10-01 16:37 Norman Wilson
2015-10-01 18:57 ` Dave Horsfall
2015-09-29  8:07 Hellwig Geisse
2015-09-29 15:35 ` scj
2015-10-01 18:00   ` Aharon Robbins
2015-09-25  2:14 Doug McIlroy
2015-09-24 17:12 Norman Wilson
2015-09-24 20:07 ` scj
2015-09-24 13:56 Noel Chiappa
2015-09-24 14:38 ` Lawrence Stewart
2015-09-24  9:27 Diomidis Spinellis
2015-09-24  9:52 ` Warren Toomey
2015-09-24 12:59 ` Clem Cole
2015-09-24 13:27 ` arnold
2015-09-24 16:12 ` John Cowan
2015-09-24 17:58 ` Jeremy C. Reed

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='CAC20D2OPd_+wTebXbeu17phaM=rDMkp+qKOUkqfkGbqssPK7ng@mail.gmail.com' \
    --to=clemc@ccc.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).