From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] pre-more pager?
Date: Wed, 8 Nov 2017 20:18:31 +0000 [thread overview]
Message-ID: <CAC20D2P+yzrbpGr9CwjkgoyS1m0n5kH7D+6tqx0dHg4SQLrMfg@mail.gmail.com> (raw)
In-Reply-To: <20171108200222.B6A6F18C0B9@mercury.lcs.mit.edu>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1441 bytes --]
On Wed, Nov 8, 2017 at 8:02 PM, Noel Chiappa <jnc at mercury.lcs.mit.edu>
wrote:
> If one were using a serial line
> hooked up to a DZ (and those were common - DH's were _much_ more
> expensive, so
> poor places like my lab at MIT used DZ's), then _every character printed_
> caused an interrupt.
Right, although many (most) Unix sites used Able DHDM's which were cheaper
than DEC DZ's, took less space in the backplane, had full modem control
(inc RTS/CTS handshaking in HW) and were DMA. But, my memory is that they
did not show up until '78 though.
The truth is DZ sucked from a performance standpoint. Besides not being
able to support RTS/CTS flow control, the 8 serial ports shared an input
buffer in the HW IIRC and the UART only had 2 chars of buffering. An
8-port DZ with all lines running 19.2K baud could kill a 780. People
that ran the "Berk-net" (which a pre-TCP networking system for UNIX that
ran on serial lines) needed spread out the Berk-Net load between different
DZ lines. No so if you have Able gear.
So I'll take the 'common' note to be if you used a 'pure DEC' set up - you
used DZ-11s. But as you said most of us were looking at costs, so
'foreign' peripherals were also 'common' in the UNIX community. DH11's
were preferred.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20171108/8d223102/attachment.html>
next prev parent reply other threads:[~2017-11-08 20:18 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-08 20:02 Noel Chiappa
2017-11-08 20:11 ` Forrest, Jon
2017-11-10 5:26 ` Random832
2017-11-10 7:31 ` Otto Moerbeek
2017-11-08 20:18 ` Clem Cole [this message]
2017-11-08 20:28 ` Ron Natalie
2017-11-08 22:47 ` Dave Horsfall
-- strict thread matches above, loose matches on Subject: below --
2017-11-09 16:19 Norman Wilson
2017-11-09 16:48 ` Arthur Krewat
2017-11-09 17:19 ` Steve Nickolas
2017-11-09 18:15 ` Don Hopkins
2017-11-09 18:26 ` Arthur Krewat
2017-11-09 13:33 Doug McIlroy
2017-11-08 22:58 Doug McIlroy
2017-11-08 22:02 Paul Ruizendaal
2017-11-08 22:20 ` Will Senn
2017-11-08 20:28 Noel Chiappa
2017-11-08 19:23 Noel Chiappa
2017-11-08 18:54 Will Senn
2017-11-08 18:59 ` Clem Cole
2017-11-08 19:06 ` Arthur Krewat
2017-11-08 19:31 ` Jeremy C. Reed
2017-11-08 22:43 ` Dave Horsfall
2017-11-08 22:47 ` Arthur Krewat
2017-11-08 23:21 ` Dave Horsfall
2017-11-09 4:38 ` Will Senn
2017-11-09 13:18 ` Dan Cross
2017-11-09 14:29 ` Will Senn
2017-11-09 20:53 ` Dave Horsfall
2017-11-10 0:15 ` Arthur Krewat
2017-11-10 2:14 ` Ralph Corderoy
2017-11-08 19:12 ` Bakul Shah
2017-11-08 19:22 ` Random832
2017-11-08 21:18 ` Will Senn
2017-11-08 21:59 ` Ron Natalie
2017-11-08 22:00 ` Clem Cole
2017-11-08 22:18 ` Will Senn
2017-11-09 2:01 ` Steve Johnson
2017-11-09 2:16 ` Lyndon Nerenberg
2017-11-08 19:29 ` Forrest, Jon
2017-11-08 19:43 ` Ron Natalie
2017-11-08 21:03 ` Mark Green
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=CAC20D2P+yzrbpGr9CwjkgoyS1m0n5kH7D+6tqx0dHg4SQLrMfg@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).