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 18:42:34 -0500 [thread overview]
Message-ID: <CAC20D2NWDuz=zQE2Z6GNc6J1+y4G9OiSyv=X5SMyd6ZB+s2vuA@mail.gmail.com> (raw)
In-Reply-To: <CANCZdfq=fv22+8DUNB2FZaNLoBikD1HvMt__AGTAFi=jZCBCsw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1468 bytes --]
👍
On Wed, Jan 22, 2020 at 6:35 PM Warner Losh <imp@bsdimp.com> wrote:
>
>
> On Wed, Jan 22, 2020 at 1:42 PM Clem Cole <clemc@ccc.com> wrote:
>
>> 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.
>>
>
> Looking at the source in the archives for V5, we see that param.h has "#define
> NOFILE 15" and for V6 we see "#define NOFILE 15 /* max open files per
> process */". V7 has "#define NOFILE 20 /* max open files per process */"
> though, so maybe you are thinking of V7 bumping the limit to 20? Or maybe
> it was a local change for MIT, since param.h could be edited... But in any
> event, I think this means that the CAC 155 reference to 16 files just means
> V6 or earlier.
>
> However, I just noticed there's more direct evidence for it being based on
> V5. On page 2 of CAC 155 we see
>
> "For further information concerning the different I/O calls the reader is
> directed to The UNIX Programmer's Manual, fifth edition, K. Thompson and D.
> M. Ritchie, June 1974."
>
> BTW, CAC 155 is the PDF we have linked from the early network page. I
> hadn't noticed before now, but seeing the missing page refreshes my
> recollection.
>
> Warner
>
--
Sent from a handheld expect more typos than usual
[-- Attachment #2: Type: text/html, Size: 3199 bytes --]
next prev parent reply other threads:[~2020-01-22 23: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
2020-01-22 23:10 ` Rob Pike
2020-01-22 23:34 ` Warner Losh
2020-01-22 23:42 ` Clem Cole [this message]
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='CAC20D2NWDuz=zQE2Z6GNc6J1+y4G9OiSyv=X5SMyd6ZB+s2vuA@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).