From: Clem Cole <clemc@ccc.com>
To: Warner Losh <imp@bsdimp.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Unix quix
Date: Wed, 22 Jan 2020 15:42:18 -0500 [thread overview]
Message-ID: <CAC20D2MA2gWX1-n_R_2_sOA_oyW2reZL1qHWDWuAy2Q_JZ=QQw@mail.gmail.com> (raw)
In-Reply-To: <CANCZdfrta7MdJSCysLJso=_+6HYY2kbfx9sNSHwn74Fem4yVvw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1382 bytes --]
On Wed, Jan 22, 2020 at 2:42 PM Warner Losh <imp@bsdimp.com> wrote:
>
> Berkeley's license was executed in January 74, so it might be on the list,
> unless there was a big delay.
>
That makes sense.
> In addition to the Nov 1975 CACM paper, there's CAC 155, published by the
> University of Illinois on 3/15/75 which pre-dates the 6th edition by a few
> months. You can read it here
> https://www.ideals.illinois.edu/bitstream/handle/2142/32547/networkunixsyste155holm.pdf?sequence=2&isAllowed=y if
> you'd like.
>
Thanks, that tells us it was 5th (BTW the PDF is missing page 1 in the scan
- although I suspect the missing info can be gleaned from RFC 681)
BTW: There is another hint in CAC 155/RFC 681. The line on page 2 that
reads: "since the user is allowed only sixteen open files." My memory is
V6 allowed more than 16, over 20 is my memory; but we would have to look at
the structure to see what it is defined as.
>
> RFC 681, dated March 18th, 1975, is another instance of an edited CAC 155
> report (it seems, I've not looked at them exactly, just a quick glance)
> that talks about this work. It's the earliest mention of Unix in an RFC
> (the next one isn't until 2 years later for an email address for Dave
> Crocker DCrocker@Rand-Unix in RFC 724 in May 1977 after which it explodes
> in references).
>
And that pretty much syncs with my memory of the time.
[-- Attachment #2: Type: text/html, Size: 4053 bytes --]
next prev parent reply other threads:[~2020-01-22 20:43 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 20:28 Rob Pike
2020-01-20 21:06 ` Adam Thornton
2020-01-22 9:31 ` Rob Pike
2020-01-22 14:57 ` Dan Cross
2020-01-22 17:54 ` Warner Losh
2020-01-22 18:01 ` Vincenzo Nicosia
2020-01-22 18:21 ` Clem Cole
2020-01-22 19:42 ` Warner Losh
2020-01-22 20:42 ` Clem Cole [this message]
2020-01-22 23:10 ` Rob Pike
2020-01-22 23:34 ` Warner Losh
2020-01-22 23:42 ` Clem Cole
2020-01-22 19:00 ` Warner Losh
2020-01-22 18:42 Noel Chiappa
2020-01-24 18:57 ` Paul Winalski
2020-01-30 4:00 ` Dave Horsfall
2020-01-30 6:32 ` Angelo Papenhoff
2020-01-22 20:49 Doug McIlroy
2020-01-22 23:06 ` Rob Pike
2020-01-23 15:56 ` Leah Neukirchen
2020-01-24 2:44 ` Warner Losh
2020-01-24 14:49 ` Clem Cole
2020-01-24 16:34 ` Jon Steinhart
2020-01-26 0:03 ` Heinz Lycklama
2020-01-24 16:40 ` Warner Losh
2020-01-24 19:38 Nelson H. F. Beebe
2020-01-24 20:05 ` Bakul Shah
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='CAC20D2MA2gWX1-n_R_2_sOA_oyW2reZL1qHWDWuAy2Q_JZ=QQw@mail.gmail.com' \
--to=clemc@ccc.com \
--cc=imp@bsdimp.com \
--cc=tuhs@minnie.tuhs.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).