From: William Corcoran <wlc@jctaylor.com>
To: Doug McIlroy <doug@cs.dartmouth.edu>
Cc: "tuhs@tuhs.org" <tuhs@tuhs.org>
Subject: Re: [TUHS] AT&T Hardware
Date: Sun, 1 Jul 2018 01:05:46 +0000 [thread overview]
Message-ID: <750E7E7B-F22B-4ECA-9CA1-247AAED3A629@jctaylor.com> (raw)
In-Reply-To: <201806301824.w5UIOO71062430@tahoe.cs.Dartmouth.EDU>
On my 3b2 310, you could always tell when the CPU were soaked at 100% utilization. The main board would actually buzz.
If you entered a CPU bound job with bc for example, you would know when the result was displayed on your terminal as the 3b2 would stop buzzing.
Truly,
Bill Corcoran
> On Jun 30, 2018, at 6:17 PM, Doug McIlroy <doug@cs.dartmouth.edu> wrote:
>
> Anent 3B's: Last time I visited Paul Allen's Living Computer Museum
> the only working Unix on display was running on a 3B2. Apparently
> the machine was robust if nothing else.
>
> doug
next prev parent reply other threads:[~2018-07-01 2:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-30 18:24 Doug McIlroy
2018-07-01 1:05 ` William Corcoran [this message]
2018-07-01 13:29 ` [TUHS] AT&T Hardware (3B2) Steve Johnson
2018-07-02 0:12 ` Lyndon Nerenberg
2018-07-02 9:56 ` Kevin Bowling
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=750E7E7B-F22B-4ECA-9CA1-247AAED3A629@jctaylor.com \
--to=wlc@jctaylor.com \
--cc=doug@cs.dartmouth.edu \
--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).