From: aps@ieee.org (Armando Stettner)
Subject: [TUHS] Questions regarding early Unix contributors
Date: Sat, 26 Sep 2015 23:52:59 -0700 [thread overview]
Message-ID: <D091DC75-9459-4973-A5FD-324D5D215D43@ieee.org> (raw)
In-Reply-To: <CAC20D2N-SUqiXuY9=T9HBrhsXLX_XQo5nNro9Uq1N9tHM543PQ@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1663 bytes --]
I actually recall him having done much of the work at CMU but can’t be sure. I also seem to recall him finish up the paper. I was lucky in my office mates: I had John Lions and tjk. Some place, I have a few pics of USG’s computer room. I only recall RP04s however. :(
aps.
> On Sep 24, 2015, at 10:28 AM, Clem Cole <clemc at ccc.com> wrote:
>
>
> On Thu, Sep 24, 2015 at 11:20 AM, Mary Ann Horton <mah at mhorton.net <mailto:mah at mhorton.net>> wrote:
> I also heard that Ted K (aka "frodo") got fsck released to Berkeley by swearing (somehow with a straight face) to the Bell Labs lawyers that it had no commercial value.
>
> That would have so much like Ted. I never heard that story, but I would believe it. I do believe that he told them (rightfully) that it was primarily developed at CMU using CMU computing resources (the 11/34A for the Digital Lab in the EE Dept that Ted and I ran). IIRC: the primary feature hat he did to it at Summit besides support for the changes in the V7 filesystems, was support for large disks (aka RP06) when attached to a small address space (11/40 class) systems, of which CMU had a number as I believe the Labs did also. Armando's I believe you two were office mates in those days, do you have memory?
>
>
> We had it at Tektronix because I brought it from CMU.
>
> Clem
>
> _______________________________________________
> TUHS mailing list
> TUHS at minnie.tuhs.org
> https://minnie.tuhs.org/mailman/listinfo/tuhs
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20150926/190ffda9/attachment.html>
next prev parent reply other threads:[~2015-09-27 6:52 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 [this message]
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
-- 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=D091DC75-9459-4973-A5FD-324D5D215D43@ieee.org \
--to=aps@ieee.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).