The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: ron@ronnatalie.com (Ron Natalie)
Subject: [TUHS] Questions for TUHS great minds
Date: Wed, 11 Jan 2017 11:25:48 -0500	[thread overview]
Message-ID: <018801d26c27$5ea34b50$1be9e1f0$@ronnatalie.com> (raw)
In-Reply-To: <CAAFR5pZBZWFLLR03+xHZng-wfJHvNxqX7WP6p=tuM4rMxmhfaw@mail.gmail.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2811 bytes --]

I give up on prediction.    I never thought UNIX would have lasted this long.    Personal computing bounces back and forth between local devices and remote services every decade or so.

 

I will offer a few interesting observations.    Back when I was still at BRL (somewhere around 1983 probably), one of my coworkers walked in and said that in a few years they'd be able to give me a computer as powerful as a VAX, and it will sit on my desk, and I’ll have exclusive use of it and be happy.    I pointed out that this was unlikely (the being happy part), as my expectations would increase as time goes on.


Ron’s Rule Of Computing:   “I need a computer ‘this’ big” (which is accompanied by holding my arms out about the width of a VAX 780 CPU cabinet.

 

Hanging up on the wall in one of the machine rooms I administered was a sign comparing the computer that had sat there (the ENIAC) to a then HP 65 calculator.     The HP 65 would have been an incredible tool to the ENIAC guys, but now It seems way dated.

 

A lot of computer discussion mentioned what would happen if a hacker had access to a CRAY computer.   Could he perhaps brute force the crypt in the UNIX password file?    Oddly, when BRL got their first Cray (an X/MP preempted from Apple’s delivery slot), I was given pretty much as much time as I wanted to try to vectorize the crypt routine.     It wasn’t particularly easy, and we had other parallel processors that were easier to program that were doing a better job at the hack for less money.    I actually signed for the BRL Cray 2 but it didn’t get installed until after I left.

 

Ron’s Rule of Software Deployment:   “Stop making cutovers on major holidays.” 

 

The dang government kept doing things like the long leader conversion on the Arpanet and the TCP/IP changeover on Jan 1.   It drove me nuts that our entire group ended up working over the holidays to bring the new systems up.    At one point when they were rejiggering the USENET groups, the proposal was to do it on Labor Day weekend.   I pointed out (this was the Atlanta UUG) that it violated the above rule AND was particularly bad because many of the USENET system admins were going to be back in Atlanta for the World Science Fiction Convention that weekend.

 

And finally, Ron’s Rule of Electrical Engineering:   “If two things can be plugged into each other, some fool will do so.   You better make it work, or at least benignly fail when it happens.”

 

Somewhere I have a cord that one of my employees made me which has a 110V plug on one side and an RJ-11 on the other (fortunately it is non functional).

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170111/61496eec/attachment.html>


  reply	other threads:[~2017-01-11 16:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-11  2:33 Robert Swierczek
2017-01-11 16:25 ` Ron Natalie [this message]
2017-01-11 16:50   ` Jacob Goense
2017-01-11 17:01     ` Corey Lindsly
2017-01-11 17:54       ` Marc Rochkind
2017-01-11 20:32       ` Jacob Goense
2017-01-11 18:34 ` Steve Johnson
2017-01-11 19:46   ` Steffen Nurpmeso
2017-01-17 13:09   ` Tim Bradshaw
2017-01-17 13:36     ` Michael Kjörling
2017-01-17 19:55     ` Steve Johnson
2017-02-01 23:32       ` Erik E. Fair
2017-01-17 14:27 Nelson H. F. Beebe

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='018801d26c27$5ea34b50$1be9e1f0$@ronnatalie.com' \
    --to=ron@ronnatalie.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).