From: schily@schily.net (Joerg Schilling)
Subject: [TUHS] BSD/v8 TCP/IP (was Shell control through external commands)
Date: Mon, 12 Sep 2016 17:27:03 +0200 [thread overview]
Message-ID: <57d6c947.hh0AnWl1uvortcSr%schily@schily.net> (raw)
In-Reply-To: <1473685007.9047.for-standards-violators@oclsc.org>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1216 bytes --]
Norman Wilson <norman at oclsc.org> wrote:
> I'm not sure of the point of this mine-is-bigger-than-yours argument, but:
>
> The earliest stream-I/O-system-based tty driver I'm aware of was
> already in the Research kernel when I interviewed at Bell Labs
> in early 1984. I have a vague memory that it was a couple of
> years older than that, and was first implemented in a post-V7
> PDP-11 system; also that I had heard about it first at a USENIX
> conference in 1982 or 1983; but I cannot find any citations to
> back up either of those memories.
Because of the design bug I mentioned, I searched for UNIX sources from AT&T
that include streams support, but could never find any.
Sun fixed the bug aprox. one year after introducing SunOS-4.0. I am sure that
if someone did use a streams based system written from the AT&T specs together
with a modern shell with an integrated history editor, the character loss would
have been detected.
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 15:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 12:56 Norman Wilson
2016-09-12 15:27 ` Joerg Schilling [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-09-12 15:41 Norman Wilson
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
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
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=57d6c947.hh0AnWl1uvortcSr%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).