The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Jim Geist <velocityboy@gmail.com>
To: Cornelius Keck <ckeck@texoma.net>
Cc: Don Hopkins <don@donhopkins.com>,
	"tuhs@minnie.tuhs.org" <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] the distinct smell of light machine oil, was Re: TUHS Digest, Vol 33, Issue 7
Date: Wed, 8 Aug 2018 12:14:19 -0700	[thread overview]
Message-ID: <CAJohCKK05su6U37B9ANc8gHs7Pnfe+5xhAFNroD2SA88dCcSHA@mail.gmail.com> (raw)
In-Reply-To: <5B6B2A78.7070303@texoma.net>

[-- Attachment #1: Type: text/plain, Size: 1363 bytes --]

I have a functional LA120 in my house and can attest to the machine smell
whenever I run it.

On Wed, Aug 8, 2018 at 11:50 AM Cornelius Keck <ckeck@texoma.net> wrote:

> Then promptly run into trouble with your SO and/or XO because they don't
> like the fragrance?
>
>
> Toby Thain wrote:
> > On 2018-08-08 10:45 AM, Clem Cole wrote:
> >>
> >>
> >> On Wed, Aug 8, 2018 at 9:51 AM, Sijmen J. Mulder <ik@sjmulder.nl
> >> <mailto:ik@sjmulder.nl>> wrote:
> >>
> >>      I'm too young to have worked with teletypes or terminals but to
> >>
> >>      __
> >>
> >>      experience what working over a slower connection would be like I
> >>      wrote____
> >>
> >>      a small pty program that throttles stdin and stdout to a given
> baud____
> >>
> >>      rate
> >>
> >> Sadly you are missing three important features in your emulation.  First
> >> the noise and the second associated motion of the carriage as the
> >> printer did its thing.  (The movement of the 'ball' (cylinder on a TTY)
> >> was magical and made it quite set of sounds you will never forget -
> >> often duplicated in the movies).   But the hardest thing to simulate is
> >> the distinct smell of light machine oil that all terminal rooms had.
> >
> > Isn't this easy? Just use a spritzer of it around your PC.
> >
> > --T
> >
> >> Clem
> >> ᐧ
> >
>

[-- Attachment #2: Type: text/html, Size: 2011 bytes --]

  reply	other threads:[~2018-08-08 19:14 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.2.1533693601.12251.tuhs@minnie.tuhs.org>
2018-08-08 12:10 ` [TUHS] " Don Hopkins
2018-08-08 12:32   ` Sijmen J. Mulder
2018-08-08 12:59     ` Don Hopkins
2018-08-08 13:51       ` Sijmen J. Mulder
2018-08-08 14:45         ` Clem Cole
2018-08-08 14:56           ` Lawrence Stewart
2018-08-08 15:09           ` [TUHS] the distinct smell of light machine oil, was " Toby Thain
2018-08-08 17:38             ` Cornelius Keck
2018-08-08 19:14               ` Jim Geist [this message]
2018-08-08 20:44                 ` Warner Losh
2018-08-09  5:14                   ` arnold
2018-08-09  5:55                     ` Jim Geist
2018-08-09  6:02                       ` George Michaelson
2018-08-09  7:20                       ` Dave Horsfall
2018-08-09 12:36                       ` Warner Losh
2018-08-09 13:45                         ` Michael Parson
2018-08-09 13:31                   ` Clem Cole
2018-08-09 14:15                     ` Derek Fawcus
2018-08-09 14:26                       ` Eric Wayte
2018-08-10 11:37                         ` Pete Turnbull
2018-08-10 11:37                       ` Pete Turnbull
2018-08-10 16:24                         ` Tom Ivar Helbekkmo via TUHS
2018-08-10 16:58                           ` Pete Turnbull

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=CAJohCKK05su6U37B9ANc8gHs7Pnfe+5xhAFNroD2SA88dCcSHA@mail.gmail.com \
    --to=velocityboy@gmail.com \
    --cc=ckeck@texoma.net \
    --cc=don@donhopkins.com \
    --cc=tuhs@minnie.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).