From: schily@schily.net (Joerg Schilling)
Subject: [TUHS] BSD/v8 TCP/IP (was Shell control through external commands)
Date: Mon, 12 Sep 2016 13:42:54 +0200 [thread overview]
Message-ID: <57d694be.ctsUTitjhmDlofic%schily@schily.net> (raw)
In-Reply-To: <14DDB012-4240-458B-AA72-5D166050F1FF@me.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1474 bytes --]
Brantley Coile <brantleycoile at me.com> wrote:
> http://articles.latimes.com/1988-01-07/business/fi-33970_1_sun-microsystems
>
> You might have the year wrong. The agreement between AT&T and Sun was announced in 1988. A year would be about right to incorporate some of the new stuff.
Well, maybe I was mistaken and 1987 was the year of NeWS and 1988 was the year
of SunOS-4.0.
> But getting back to your original comment that you are not aware of any streams implementation before SunOS-4.0, do you mean that it was the first you became aware of? Certainly System V, from whence it came, predated SunOS-4.0 and 8th Edition predated that. My copy of the tty_ld(4) man page was printed Feb 10, 1985.
SVr4 was the first "SystemV" with a streams based tty driver and this driver
was the driver taken from SunOS-4.0. You can verify this by looking at the
bug-fix that was needed to make it work at all.
The AT&T concept had a bug as it did not allow to switch from raw mode to cooked mode
mode without loosing all characters in the buffer. Sun fixed this by
introducing a new mesage that says: Someone is going to read 5 chars, so
transfer 5 chars from the edit-buffer upstream but keep the rest.
Jörg
--
EMail:joerg at schily.net (home) Jörg Schilling D-13353 Berlin
joerg.schilling at fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.org/private/ http://sourceforge.net/projects/schilytools/files/'
next prev parent reply other threads:[~2016-09-12 11:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 1:31 [TUHS] Shell control through external commands Norman Wilson
2016-09-12 4:44 ` [TUHS] BSD/v8 TCP/IP (was Shell control through external commands) Greg 'groggy' Lehey
2016-09-12 5:24 ` Warner Losh
2016-09-12 5:38 ` Cory Smelosky
2016-09-12 5:48 ` Erik E. Fair
2016-09-12 9:22 ` Joerg Schilling
2016-09-12 10:25 ` Brantley Coile
2016-09-12 11:00 ` Joerg Schilling
2016-09-12 11:16 ` Brantley Coile
2016-09-12 11:42 ` Brantley Coile
2016-09-12 11:42 ` Joerg Schilling [this message]
2016-09-12 7:20 ` Greg 'groggy' Lehey
2016-09-12 18:32 ` Clem Cole
2016-09-13 10:52 ` Tony Finch
2016-09-13 12:54 ` Clem Cole
2016-09-12 9:33 ` [TUHS] Shell control through external commands Joerg Schilling
2016-09-12 12:56 [TUHS] BSD/v8 TCP/IP (was Shell control through external commands) Norman Wilson
2016-09-12 15:27 ` Joerg Schilling
2016-09-12 15:41 Norman Wilson
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=57d694be.ctsUTitjhmDlofic%schily@schily.net \
--to=schily@schily.net \
/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).