The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: arnold@skeeve.com (arnold@skeeve.com)
Subject: [TUHS] networking on unix before uucp
Date: Mon, 25 Aug 2014 13:20:52 -0600	[thread overview]
Message-ID: <201408251920.s7PJKqCr032295@freefriends.org> (raw)
In-Reply-To: <53FB8806.7090906@e-bbes.com>

> On 2014-08-25 09:49, arnold at skeeve.com wrote:
> > I too used a blit for a while. It sure could easily kill a vax/780.

emanuel stiebler <emu at e-bbes.com> wrote:
> Sorry, what do you mean by that?

We had a vax 11/780, with serial lines to various peoples' offices.
BSD 4.1 at the time IIRC, later 4.2.  The whole ICS dept. at Ga Tech
was using it - faculty and grad students and lab staff (which I was one
of). The load average was constantly in the single digits.

Now add a few blits, where each physical terminal is doing the load of
4-6 virtual ones (using pseudo-ttys) - a shell on each pty and commands
running on each pty.  Bingo! The load average shoots way up.

So, the blit itself wasn't at fault.  All the people taking advantage
of what it could let them do, was.  At some point they wanted the lab
staff to stop using them because of this...

Arnold



  reply	other threads:[~2014-08-25 19:20 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-23  3:08 Brian Walden
2014-08-23 18:02 ` Sven Mascheck
2014-08-23 19:32 ` Clem Cole
2014-08-24  4:59   ` Larry McVoy
     [not found]     ` <53FB4B6D.5070404@e-bbes.com>
2014-08-25 14:45       ` Larry McVoy
2014-08-25 15:22         ` A. P. Garcia
2014-08-25 15:49         ` arnold
2014-08-25 19:01           ` emanuel stiebler
2014-08-25 19:20             ` arnold [this message]
2014-08-25 20:00               ` Lyndon Nerenberg
2014-08-25 21:06                 ` John Cowan
2014-08-25 21:14                   ` Lyndon Nerenberg
2014-08-25 21:17                     ` Lyndon Nerenberg
2014-08-26  3:26                 ` Larry McVoy
2014-08-26  6:17                   ` arnold
  -- strict thread matches above, loose matches on Subject: below --
2014-08-26 16:56 Noel Chiappa
2014-08-26  6:44 Jason Stevens
2014-08-22 16:35 Noel Chiappa
2014-08-22 13:27 Noel Chiappa
2014-08-22 13:32 ` Ronald Natalie
2014-08-22 13:35 ` Ronald Natalie
2014-08-22  3:42 Mark Longridge
2014-08-22 15:09 ` Mary Ann Horton
2014-08-22 22:12   ` Cory Smelosky
2014-08-24 22:46     ` Clem Cole
2014-08-24 23:00       ` Clem Cole
2014-08-24 23:07       ` A. P. Garcia
2014-08-24 23:43         ` Clem Cole
2014-08-25 14:21         ` Ronald Natalie
2014-08-26 16:36     ` Jeremy C. Reed
2014-08-26 23:20       ` Clem Cole
2014-08-22 15:18 ` Dan Cross
2014-08-22 15:20   ` Dan Cross
2014-08-22 15:57   ` John Cowan
2014-08-22 16:06     ` Ronald Natalie
2014-08-22 18:11       ` Dave Horsfall
2014-08-22 17:51         ` Larry McVoy
2014-08-22 19:24           ` John Cowan
2014-08-22 20:37           ` Dave Horsfall
2014-08-22 20:16             ` Larry McVoy
     [not found]               ` <alpine.BSF.2.00.1408230659490.42071@aneurin.horsfall.org>
2014-08-23  2:30                 ` Larry McVoy
2014-08-22 19:32         ` John Cowan
2014-08-22 18:01 ` Dave Horsfall

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=201408251920.s7PJKqCr032295@freefriends.org \
    --to=arnold@skeeve.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).