From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] 2.10
Date: Thu, 20 Nov 2014 23:46:26 -0600 [thread overview]
Message-ID: <CAC20D2PJBmcqtOYcnMgMwkpUCBfoPCjoPrU2ZnSQMea+DR001A@mail.gmail.com> (raw)
In-Reply-To: <alpine.GSO.2.03.1411202351250.646@gewt.net>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1551 bytes --]
On Thu, Nov 20, 2014 at 10:55 PM, Cory Smelosky <b4 at gewt.net> wrote:
> Well, 2.10 has SLIP,
SLIP means you still need the IP stack
(serial-line-ip)
. It
just replaces an ethernet driver with a serial port.
> but it'd certainly be easier to implement a simple userland tool to talk
> to a frontend!
Actually there was tool that was almost all in userland to support
multiple sessions over single serial line between a Macs a UNIX system. My
memory is that it used Chesson's multiplexer (mpx) which is part of stock
V7 (his is pre-select system call). I wish I could remember the name of
that program. But I bet it or something like it could be repurposed pretty
quickly to talk to a frontend micro.
Biggest issue is interrupt overhead on serial ports on the 11. If this is
real HW, see you can find a real DEC DH or better yet - an Able DH/DM. DH
style interfaces will be a huge difference over DL's or DZs. DZs were pigs
on Vaxen and on an 11 a line at 19.2K continuous could kill it.
BTW: I thought of another option. It's not telnet or ftp, but if your
desire is move files back and forth without having to use a common physical
media and sneaker-net, BSD 2x should have the BerkNET code in it. That
will run on an serial line - although my previous comment about the type of
interface can matter from a performance standpoint.
Clem
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20141120/ab5a1bb6/attachment.html>
next prev parent reply other threads:[~2014-11-21 5:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 1:32 Jacob Ritorto
2014-11-21 1:56 ` Nick Downing
[not found] ` <CA+oaVqwGKiOPKm8Bz62Z0s9dEYiAbTXR9=WrQyjqGFX-uaYmjQ@mail.gmail.com>
2014-11-21 3:25 ` Jacob Ritorto
2014-11-21 3:36 ` Cory Smelosky
2014-11-21 4:02 ` Cory Smelosky
2014-11-21 4:43 ` Clem Cole
2014-11-21 4:55 ` Cory Smelosky
2014-11-21 5:46 ` Clem Cole [this message]
2014-11-21 6:07 ` Cory Smelosky
2014-11-26 6:28 ` [TUHS] BerkNet Erik E. Fair
2014-11-26 6:48 ` Cory Smelosky
2014-11-27 16:42 ` Mary Ann Horton
2014-11-29 16:38 ` Clem Cole
2014-11-26 18:24 ` Clem Cole
2014-11-26 18:35 ` Dan Cross
2014-11-26 20:03 ` Clem Cole
2014-11-26 18:26 ` Dave Horsfall
2014-11-21 6:13 ` [TUHS] 2.10 Jacob Ritorto
2014-11-21 13:06 ` Clem Cole
2014-11-21 15:37 Noel Chiappa
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=CAC20D2PJBmcqtOYcnMgMwkpUCBfoPCjoPrU2ZnSQMea+DR001A@mail.gmail.com \
--to=clemc@ccc.com \
/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).