The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: clemc@ccc.com (Clem cole)
Subject: [TUHS] What was the first edition of UNIX that left AT&T
Date: Fri, 1 Sep 2017 20:24:31 -0400	[thread overview]
Message-ID: <6A1D6BAF-E3B4-4DA2-B198-FD0929232A83@ccc.com> (raw)
In-Reply-To: <D66F0B83-AC94-4A47-9847-D709D8BAAE27@ccc.com>

I did hear back from Lou Katz - user #1.  Indeed the first version that escaped the labs was the 4th edition. 

Sent from my PDP-7 Running UNIX V0 expect things to be almost but not quite. 

> On Sep 1, 2017, at 7:16 PM, Clem cole <clemc at ccc.com> wrote:
> 
> Interesting. If O'Malley had a connection wonder what it was connected too on both sides.  It had to be to lbl but the Vdh was a piece of shit even in the ingvax days.  The first version was even worse.  On the ucb side I wonder.  It would not have been Unix because UofI did the original arpanet code and that was for v6.  There was never a pdp10 at ucb so I wonder if it was one of the CDC machines which were the primary systems until Unix came to be.  
> 
> Sent from my PDP-7 Running UNIX V0 expect things to be almost but not quite. 
> 
>>> On Sep 1, 2017, at 5:59 PM, Jeremy C. Reed <reed at reedmedia.net> wrote:
>>> 
>>> On Fri, 1 Sep 2017, Clem Cole wrote:
>>> 
>>> So it means that UCB was hacking privately without taking to Katz@ NYU, or
>>> the Columbia and Harvard folks for a while.   I need to ask Lou what he
>>> remembers.   UCB was not connected to the Arpanet at this point (Stanford
>>> was), so it's possible Ken's sabbatical openned up some channels that had
>>> not existed.   [UCB does not get connected until ing70 gets the
>>> vdh-interface up the hill to LBL's IMP as part of the Ingress project and
>>> that was very late in the 70s  - not long before I arrived]. 
>> 
>> Allman told me that Mike O'Malley had an ARPA connection at UCB that was 
>> axed a few years before the INGRES link. So yes, I think no Arpanet 
>> connection during the early BSD development work. (Losing this 
>> connection may have had some controversy, but I don't know the details.)
>> 
>> Fabry told me that O'Malley used Unix for his (EECS) Artificial 
>> Intelligence research projects before he discovered it (so before the 
>> October 1973 Symposium).
>> 
>> RFC 402 of Oct 1972 has a ARPA network participant Michael O'Malley of 
>> University of Michigan Phonetics Laboratory. Also this draft report at 
>> http://digitalcollections.library.cmu.edu/awweb/awarchive?type=file&item=355330 
>> about the ARPA speech recognition project lists M. H. O'Malley at UCB 
>> and says the principle investigator from Univ. of Michigan moved to UCB.  
>> (I never go ahold of him to see if had any other relevance to my BSD 
>> story.)
>> 
>> 


  parent reply	other threads:[~2017-09-02  0:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-31 22:33 Clem Cole
2017-08-31 23:20 ` Theo Pavlidis
2017-08-31 23:27 ` Warren Toomey
2017-09-01 19:05   ` Jeremy C. Reed
2017-09-01 19:58     ` Clem Cole
2017-09-01 21:59       ` Jeremy C. Reed
     [not found]         ` <D66F0B83-AC94-4A47-9847-D709D8BAAE27@ccc.com>
2017-09-02  0:24           ` Clem cole [this message]
2017-09-02  1:51             ` Jeremy C. Reed
2017-09-02  2:12 Noel Chiappa

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=6A1D6BAF-E3B4-4DA2-B198-FD0929232A83@ccc.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).