Computer Old Farts Forum
 help / color / mirror / Atom feed
From: Rod Bartlett via COFF <coff@tuhs.org>
To: segaloco <segaloco@protonmail.com>
Cc: COFF <coff@tuhs.org>
Subject: [COFF] Re: Smokin' In the Terminal Room
Date: Fri, 29 Sep 2023 05:39:48 -0400	[thread overview]
Message-ID: <AED3DDF8-6752-48F2-A1A7-C81955E04A0C@mac.com> (raw)
In-Reply-To: <kCWRaGdEQbYcLzKLtskm8W8TwuJNOFazJfTJd2zItrppXPdUqBnbTovqYA-9NTQ5AUqrRe2uX8KYR3TaReOP7xRPbg5c-xalfkbVIsFj3fY=@protonmail.com>

I worked as a field engineer on Honeywell mainframes in the late 1970s and I regularly observed people smoking in terminal rooms.  There wasn't much in those old CRT terminals which could be damaged by smoke.  Some sites also allowed computer operators to smoke at the consoles or while hanging tapes.  The worst instance I saw was at a site which had an old GE 635 mainframe.  The onsite field engineer was a heavy smoker and used the oscilloscope cart tray as an ashtray.  That held many years worth of evidence of indulgence near equipment.

There were heavy duty air conditioners in those computer rooms which kept the air moving and being filtered.  It probably would have been more damaging near minicomputers which often didn't require the constant A/C.  The disk drives also had large air filters which removed particulates from the air while operating but there was always the chance that smoke particles could enter while a disk pack was being mounted.

By the time I left the mainframe environment in the late 1980s, smoke was much less common around equipment with most sites forcing smokers to either go outside or to use designated smoking rooms.

 - Rod

> On Sep 28, 2023, at 11:03 PM, segaloco via COFF <coff@tuhs.org> wrote:
> 
> Subject doesn't roll off the tongue like the song, but hey, I got a random thought today and I'd be interested in experiences.  I get where this could be a little...controversial, so no pressure to reply publicly or at all.
> 
> Was it firmly held lore from the earliest days to keep the air as clean as possible in computer rooms in the earlier decades of computing?  What has me asking is I've seen before photos from years past in R&D and laboratory settings where whoever is being photographed is happy dragging away on a cigarette (or...) whilst surrounded by all sorts of tools, maybe chemicals, who knows.  It was a simpler time, and rightfully so those sorts of lax attitudes have diminished for the sake of safety.  Still I wonder, was the situation the same in computing as photographic evidence has suggested it is in other such technical settings?  Did you ever have to deal with a smoked out server room that *wasn't* because of thermal issues with the machinery?
> 
> I hope this question is fine by the way, it's very not tech focused but I also have a lot of interest in the cultural shifts in our communities over the years.  Thanks as always folks for being a part of one of the greatest stories still being told!
> 
> - Matt G.


      parent reply	other threads:[~2023-09-29  9:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-29  3:03 [COFF] " segaloco via COFF
2023-09-29  7:07 ` [COFF] " Lars Brinkhoff
2023-09-29  7:24   ` Lars Brinkhoff
2023-09-29  9:39 ` Rod Bartlett via COFF [this message]

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=AED3DDF8-6752-48F2-A1A7-C81955E04A0C@mac.com \
    --to=coff@tuhs.org \
    --cc=norwayjose@mac.com \
    --cc=segaloco@protonmail.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).