From: "Douglas A. Gwyn" <DAGwyn@null.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] sam -r
Date: Thu, 5 Feb 2004 09:49:56 +0000 [thread overview]
Message-ID: <PYudnVGigOKvJ7zdRVn-gw@comcast.com> (raw)
In-Reply-To: <024e01c3eb61$1f4ed140$67844051@SOMA>
Don't forget, the original sam protocol is flawed in
regard to terminating the (remote) connection, since
the host terminal handler can change mode and echo a
packet that hasn't yet arrived. Of course the echoed
characters screw up the local samterm. We fixed this
long ago in the BRL version of "sam", by adding one
extra handshake at the very end.
prev parent reply other threads:[~2004-02-05 9:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-04 20:54 boyd, rounin
2004-02-05 9:49 ` Douglas A. Gwyn [this message]
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=PYudnVGigOKvJ7zdRVn-gw@comcast.com \
--to=dagwyn@null.net \
--cc=9fans@cse.psu.edu \
/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).