The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: clemc@ccc.com (Clem cole)
Subject: [TUHS] Unix v6 problem with /tmp
Date: Wed, 27 Jul 2016 20:47:32 -0400	[thread overview]
Message-ID: <E99C35C3-EA27-453A-95F3-B4D9775FF72C@ccc.com> (raw)
In-Reply-To: <1469654287.23225.for-standards-violators@oclsc.org>

Certainly 4.2 was were most people found them and the UNIX community at large saw them and I do not wAnt to disparage my siblings at Berkeley for the fine work done there. 


 But particularly since Dennis has passed I hate seeing history get forgotten/rewritten.  I can tell you I personally I remember talking to Dennis and Steve Bourne about the idea of late binding for nami pre-BSD 3x UNIX days  - late 1979 is my guess might have been a little later.  Dennis would have been messing with them in a post V7 systems.  I would have been at Tek @ the time.  Joy probable would have seen them as a summer intern at the labs and talked to him about it then.  

You are right the BSD 4.2 made the world know about them but like a number of things in BSD (such as networking) it was in some cases a (better) integration of ideas others had played with before. 




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

> On Jul 27, 2016, at 5:18 PM, Norman Wilson <norman at oclsc.org> wrote:
> 
> I'm pretty sure they came from Berkeley nevertheless


  reply	other threads:[~2016-07-28  0:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-27 21:18 Norman Wilson
2016-07-28  0:47 ` Clem cole [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-07-27 20:41 Norman Wilson
2016-07-27 20:28 Mark Longridge
2016-07-27 20:31 ` William Pechter
2016-07-27 20:57   ` Clem Cole
2016-07-27 21:01     ` Clem Cole
2016-07-27 21:10     ` William Pechter
2016-07-28  0:49       ` Clem cole
2016-07-28  1:03         ` William Pechter
2016-07-28  1:03       ` Clem cole

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=E99C35C3-EA27-453A-95F3-B4D9775FF72C@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).