From: usotsuki@buric.co (Steve Nickolas)
Subject: [TUHS] Names of famous, historical UNIX machines?
Date: Wed, 1 Feb 2017 17:20:47 -0500 (EST) [thread overview]
Message-ID: <alpine.BSF.2.02.1702011719520.11360@frieza.hoshinet.org> (raw)
In-Reply-To: <20170201220848.GH880@mcvoy.com>
On Wed, 1 Feb 2017, Larry McVoy wrote:
> There was a phone in there and it would ring and a sales guy would pick
> it up saying "Moshi, Moshi" which I took to mean "Hi" or "hello".
>
> It was always corporate calling to see how things were going.
>
> So one day I'm in there by myself and the phone rings and without thinking
> about it (I don't speak Japanese so WTF was I thinking?), I pick it up
> and say "Mushi, Mushi". Too which I get a stream of horrified Japanense
> and I just hang up.
>
> The sales guys show later and I say "I answered a call for you". "Oh,
> yeah, what did you say?" "Mushi, mushi". Stunned silence and then they
> are rolling on the floor laughing.
>
> I'm going "What? What did I do?".
>
> They say "Corporate called to find out how things are going and the
> software guy said 'bug, bug' and hung up".
>
> We all went out drinking that night, those sales guys were all right.
> Seemed sort of cold before that but we were buds from there forward.
> I'll bet you a pile of money somewhere there is a sales guy in Japan
> who tells this story, probably not in a way that is flattering to me :)
>
> (Note this about 30 years ago and I can't remember if Moshi is hi or if it
> is Mushi that is hi, but you get the idea).
>
> --larry "bug, bug" mcvoy
>
You were right - "moshi-moshi" is "hello" and "mushi" is bug.
(I picked up a little bit of Japanese from 20 years of watching anime...
lol)
-uso.
next prev parent reply other threads:[~2017-02-01 22:20 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-01 20:43 Michael Kjörling
2017-02-01 20:46 ` Clem Cole
2017-02-01 20:50 ` Clem Cole
2017-02-01 21:11 ` Lars Brinkhoff
2017-02-01 21:20 ` Noel Chiappa
2017-02-01 21:42 ` Michael Kjörling
2017-02-01 21:43 ` Cory Smelosky
2017-02-01 22:16 ` Cory Smelosky
2017-02-01 21:50 ` William Pechter
2017-02-01 22:06 ` Clem Cole
2017-02-01 22:11 ` Larry McVoy
2017-02-01 22:21 ` Clem Cole
2017-02-01 22:28 ` Clem Cole
2017-02-01 22:44 ` William Pechter
2017-02-02 1:14 ` Rico Pajarola
2017-02-02 1:34 ` Clem Cole
2017-02-02 1:18 ` Clem Cole
2017-02-02 1:29 ` Clem Cole
2017-02-02 13:11 ` arnold
2017-02-04 3:46 ` Steve Johnson
2017-02-04 3:56 ` Larry McVoy
2017-02-04 22:48 ` Nemo
2017-02-01 22:26 ` Arthur Krewat
2017-02-02 7:38 ` Lars Brinkhoff
2017-02-01 21:33 ` Larry McVoy
2017-02-01 21:57 ` Clem Cole
2017-02-01 22:08 ` Larry McVoy
2017-02-01 22:20 ` Steve Nickolas [this message]
2017-02-03 1:51 ` Dave Horsfall
2017-02-01 22:54 ` Jacob Goense
2017-02-03 12:59 ` Tim Bradshaw
2017-02-03 14:04 ` Dave Horsfall
2017-02-03 14:11 ` Jacob Goense
2017-02-03 15:12 ` Arthur Krewat
2017-02-06 5:41 ` Dave Horsfall
2017-02-03 5:50 ` Lars Brinkhoff
2017-02-01 22:16 Noel Chiappa
2017-02-01 22:27 Berny Goodheart
2017-02-02 9:59 Rudi Blom
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.02.1702011719520.11360@frieza.hoshinet.org \
--to=usotsuki@buric.co \
/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).