The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Rich Morin <rdm@cfcl.com>
To: TUHS <tuhs@tuhs.org>
Subject: [TUHS] Re: Early Unix and Keyboard Skills
Date: Thu, 3 Nov 2022 12:36:45 -0700	[thread overview]
Message-ID: <188181D2-1198-49EF-B4F1-BB3617CCC215@cfcl.com> (raw)
In-Reply-To: <CAD2gp_Toj2HMwg1gGkAvWkKTgDMiK8O2Hj4KAWRqoDPp5yzxhg@mail.gmail.com>

> On Thu, Nov 3, 2022 at 11:19 AM Paul Winalski <paul.winalski@gmail.com> wrote:
>  
> The model 33 had a very fast and powerful carriage return mechanism,
> good for cracking walnuts ...

In 1968, San Francisco State College (now yclept "University") set up a "computer lab", based on a few IBM 2741 terminals.  These were hooked by leased lines to Stanford's Wylbur system and allowed us to do line-based editing, interactive Lisp, etc.

Anyway, the terminals were based on the I/O Selectric, and the ball impacts were powered by a spinning bar with pretty much infinite torque.  One day, an insufficiently cautious TA got her long, straight hair wound onto the bar.  Each character that was printed pulled her head closer to the terminal.

Fortunately, someone hit the OFF switch in time to avoid bloodshed.  Then, we were able to carefully unwind her hair and free her from the terminal.  IIRC, we didn't even have to cut any of her hair in the process...

-r


  reply	other threads:[~2022-11-03 19:38 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-02  2:36 [TUHS] " steve jenkin
2022-11-02  6:53 ` [TUHS] " Michael Kjörling
2022-11-02  7:11   ` Rob Pike
2022-11-02 13:28     ` Clem Cole
2022-11-03 21:51     ` Stuff Received
2023-08-05 23:53     ` scj
2023-08-06  0:22       ` KenUnix
2023-08-06  0:43         ` Larry McVoy
2023-08-06 14:51           ` Leah Neukirchen
2023-08-06 15:01             ` Larry McVoy
2023-08-06 16:31             ` Clem Cole
2023-08-06 18:20               ` Jon Forrest
2023-08-07  4:56                 ` Adam Thornton
2023-08-06  8:37       ` Ronald Natalie
2022-11-02 12:13 ` Steffen Nurpmeso
2022-11-02 12:24   ` Steffen Nurpmeso
2022-11-02 20:35     ` Ron Natalie
2022-11-02 12:26   ` John P. Linderman
2022-11-02 13:07     ` Larry Stewart
2022-11-02 13:16       ` Larry McVoy
2022-11-02 13:27     ` Steffen Nurpmeso
2022-11-02 19:01 ` jason-tuhs
2022-11-02 19:20   ` John P. Linderman
2022-11-03  1:47     ` Ronald Natalie
2022-11-03  1:59       ` Dave Horsfall
2022-11-03  3:01       ` Clem Cole
2022-11-03 15:17       ` Paul Winalski
2022-11-03 16:18         ` Clem Cole
2022-11-03 17:02         ` John Cowan
2022-11-03 19:36           ` Rich Morin [this message]
2022-11-03 20:01             ` Charles H Sauer (he/him)
2022-11-02 12:16 Douglas McIlroy

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=188181D2-1198-49EF-B4F1-BB3617CCC215@cfcl.com \
    --to=rdm@cfcl.com \
    --cc=tuhs@tuhs.org \
    /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).