From: dave@horsfall.org (Dave Horsfall)
Subject: [TUHS] Ken visits Cray Research Inc and finds old bug
Date: Mon, 13 Nov 2017 09:57:46 +1100 (EST) [thread overview]
Message-ID: <alpine.BSF.2.21.1711130952470.36729@aneurin.horsfall.org> (raw)
In-Reply-To: <CAP6exYLgXZ3inuXZ_AHSo2i=d_pECA0R6vs61XCtitySf+HFjQ@mail.gmail.com>
On Sun, 12 Nov 2017, ron minnich wrote:
> There's a story I heard once in supercomputing circles from the 80s,
> that Ken visited CRI in Minneapolis, sat down at the console of a
> machine running the then-new port of Unix to one of the Crays, typed a
> command, and said something like "ah, that bug is still there." Anybody
> know what the bug was?
I remember the story too; I think it was one of the text tools (grep, sed,
I dunno), but yeah, a reference would be nice (at least for the archives).
--
Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer."
next prev parent reply other threads:[~2017-11-12 22:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-12 3:41 ron minnich
2017-11-12 22:57 ` Dave Horsfall [this message]
2017-11-13 5:10 ` Ken Thompson
2017-11-13 14:14 ` Larry McVoy
2017-11-13 15:13 ` Don Hopkins
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=alpine.BSF.2.21.1711130952470.36729@aneurin.horsfall.org \
--to=dave@horsfall.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).