The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: William Corcoran <wlc@jctaylor.com>
To: "John P. Linderman" <jpl.jpl@gmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] ATT Hardware
Date: Mon, 2 Jul 2018 00:20:42 +0000	[thread overview]
Message-ID: <927BB205-49F8-492B-8AAB-0395F36B549A@jctaylor.com> (raw)
In-Reply-To: <CAC0cEp-XcnX+Vbhw0__sp=byKbAA11+ZD=krCsYeFMbp-1GXtA@mail.gmail.com>

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

No! no! no!  The 3b2 was one of the first supermicros to fully integrate power management with the system.   Yanking the cord would be unthinkable mainly because it was unnecessary.  The shutdown script would remove power to the the system once the system safely went down and buffers were flushed.   You could also depress this massive rocket switch on the side of the unit and it would kick off the powerdown script.  It is noteworthy that the 3b2 power switch was stateless...allowing human and computer to turn off the power.

Finally, the 3b2 is probably the only system in the world with system diagnostics so in depth that they were nearly as significant as the operating system.   It’s a telecommunications thing.   Interestingly,  the color of the 3b2 was similar to a VAX Brown and White.


On Jul 1, 2018, at 6:24 PM, John P. Linderman <jpl.jpl@gmail.com<mailto:jpl.jpl@gmail.com>> wrote:

Puns aside, anyone who didn't consider pulling the plug was probably not someone who should be bringing the system down.

On Sat, Jun 30, 2018 at 10:17 PM, Greg 'groggy' Lehey <grog@lemis.com<mailto:grog@lemis.com>> wrote:
On Saturday, 30 June 2018 at  7:15:07 -0400, Norman Wilson wrote:
> Ron Natalie:
>
>   My favorite 3B2ism was that the power switch was soft (uncommon then, not so
>   much now).   I seem to recall that if the logged in user wasn't in a
>   particular group, pushing the power button was a no-op.   You didn't have
>   sufficient privs to operate the power.
>
> ====
>
> Surely you mean the current user didn't have sufficent power.

Or was experiencing too much resistance?

Greg
--
Sent from my desktop computer.
Finger grog@lemis.com<mailto:grog@lemis.com> for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA


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

  reply	other threads:[~2018-07-02  0:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-30 11:15 Norman Wilson
2018-07-01  2:17 ` Greg 'groggy' Lehey
2018-07-01 20:14   ` John P. Linderman
2018-07-02  0:20     ` William Corcoran [this message]
2018-07-02  0:55       ` John P. Linderman
2018-07-02  3:59         ` William Corcoran
2018-07-02 10:13       ` Kevin Bowling
2018-07-03  1:02     ` Dave Horsfall
  -- strict thread matches above, loose matches on Subject: below --
2018-06-29 13:16 ron
2018-06-29 14:55 ` John P. Linderman
2018-06-29 15:07   ` Clem Cole
2018-06-29 16:31   ` ron
2018-06-29 17:51     ` Seth J. Morabito
2018-06-29 15:26 ` Seth J. Morabito
2018-06-29 16:29   ` ron
2018-06-29 18:48 ` Perry E. Metzger

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=927BB205-49F8-492B-8AAB-0395F36B549A@jctaylor.com \
    --to=wlc@jctaylor.com \
    --cc=jpl.jpl@gmail.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).