The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Pete Turnbull <pete@dunnington.plus.com>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] the distinct smell of light machine oil, was Re: TUHS Digest, Vol 33, Issue 7
Date: Fri, 10 Aug 2018 12:37:45 +0100	[thread overview]
Message-ID: <d0fd5b21-65d3-e9ea-6b3e-c55897e10d28@dunnington.plus.com> (raw)
In-Reply-To: <20180809141509.GA91112@accordion.employees.org>

On 09/08/2018 15:15, Derek Fawcus wrote:
> On Thu, Aug 09, 2018 at 09:31:39AM -0400, Clem Cole wrote:
>> Hmmrrph.... Youngsters...    WD40 is silcon based.
> 
> I didn't know that; never I checked the can; but yeah a distinctive smell...

Ordinary WD40 is NOT silicone based (obNitPick: note the 'e': not 
silicon, which is a hard crystalline substance).  There is a 
"specialist" silicone-based version but ordinary WD40 is hydrocarbon 
based, being a mixture of light paraffin (naptha to transpondians, ie 
the stuff that's used as a solvent or fuel) and a paraffin wax, as 
stated in the manufacturer's official MSDS document.

The characteristic smell is largely from an aromatic hydrocarbon additive.

>> Real "3 in One" oil
>> (came in a small can) is light machine oil but you can still get it:
> 
> Yup, useful on bike chains and oilstones (as in sharpening chisels and planes).

And not much else, because like a lot of simple hydrocarbon oils 
developed half a century or more ago, it oxidises to a gummy substance.

The Teletype manual definitely doesn't suggest 3-in-One oil and some 
sources suggest it's too thick anyway.  The manual in front of me 
specifies two Western Electric part numbers for oil and grease.  It's 
been discussed more than once on the Greenkeys list, and there's a 
useful page listing modern equivalents at Doug Jones' page:
https://homepage.cs.uiowa.edu/~jones/pdp8/UI-8/ks7470oil.shtml

-- 
Pete
Pete Turnbull

  parent reply	other threads:[~2018-08-10 11:53 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
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 [this message]
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=d0fd5b21-65d3-e9ea-6b3e-c55897e10d28@dunnington.plus.com \
    --to=pete@dunnington.plus.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).