From: hc05@summitis.com (Beirne Konarski)
To: sam-fans@hawkwind.utcs.toronto.edu (Sam mailing list)
Subject: rsh replacement
Date: Thu, 23 Dec 1993 11:38:26 -0500 [thread overview]
Message-ID: <9312231626.AA61932@rexsrvr2.summitis.com> (raw)
I am attempting to run sam over SNA rather than TCP/IP. This means
that I had to write an rsh equivalent for LU6.2. I have it done as
near as I can tell(I can do ed with it), but sam does not work. From
looking at the line trace I find that no data is moving between samterm
and sam. My question is, what is sam expecting from rsh? Does sam
send lines back and forth? Should my rsh replacement read a character
at a time from sam? I am trying to send blocks of data rather than
individual characters over the line.
Beirne
--
-------------------------------------------------------------------------------
Beirne Konarski | Reading maketh a full man, conference a
beirnek@summitis.com | ready man, and writing an exact man.
"Untouched by Scandal" | -- Francis Bacon
-------------------------------------------------------------------------------
reply other threads:[~1993-12-23 16:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=9312231626.AA61932@rexsrvr2.summitis.com \
--to=hc05@summitis.com \
--cc=sam-fans@hawkwind.utcs.toronto.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).