From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
To: tuhs@tuhs.org
Cc: jnc@mercury.lcs.mit.edu
Subject: Re: [TUHS] V6 networking & alarm syscall
Date: Fri, 11 Jan 2019 23:14:01 -0500 (EST) [thread overview]
Message-ID: <20190112041401.A672D18C073@mercury.lcs.mit.edu> (raw)
> From: Dave Horsfall
> As I dimly recall ... it returns the number of characters in the input
> queue (at that time)
Well, remember, this is the MIT V6 PDP-11 system, which had a tty driver which
had been completely re-written at MIT years before, so you'd really have to
check the MIT V6 sources to see exactly what it did. I suspect they borrowed
the name, and basic semantics, from Berkeley, but everything else - who
knows.
This user telnet is from 1982 (originally), but I was looking at the final
version, which is from 1984; the use of the ioctl was apparently a later
addition. I haven't checked to see what it did originally for reading from the
user's terminal (although the earlier version also used the 'tasking'
package).
Noel
next reply other threads:[~2019-01-12 4:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-12 4:14 Noel Chiappa [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-01-13 10:52 Paul Ruizendaal
2019-01-13 15:39 ` Warner Losh
[not found] <mailman.1.1547258402.6716.tuhs@minnie.tuhs.org>
2019-01-12 11:13 ` Paul Ruizendaal
2019-01-12 1:24 Noel Chiappa
2019-01-12 1:58 ` Dave Horsfall
2019-01-12 2:33 ` Warner Losh
2019-01-11 23:27 Paul Ruizendaal
2019-01-10 23:12 Paul Ruizendaal
2019-01-11 0:17 ` Clem cole
2019-01-11 15:33 ` ron
2019-01-11 18:45 ` Clem Cole
2019-01-11 19:06 ` David
2019-01-11 22:08 ` reed
2019-01-11 22:18 ` Larry McVoy
2019-01-12 12:04 ` reed
2019-01-12 17:20 ` Clem Cole
2019-01-12 18:16 ` Eric Allman
2019-01-13 1:16 ` Madeline Autumn-Rose
2019-01-11 22:47 ` Clem Cole
2019-01-11 22:55 ` Eric Allman
2019-01-11 23:32 ` Warner Losh
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=20190112041401.A672D18C073@mercury.lcs.mit.edu \
--to=jnc@mercury.lcs.mit.edu \
--cc=tuhs@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).