From: "Albert D. Cahalan" <acahalan@cs.uml.edu>
To: davidsen@tmr.com (Bill Davidsen)
Cc: acahalan@cs.uml.edu (Albert D. Cahalan),
j.schmidt@paradise.net.nz (Jens Schmidt),
root@chaos.analogic.com, phillips@arcor.de (Daniel Phillips),
arodland@noln.com (Andrew Rodland),
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -ac] Panicking in morse code
Date: Mon, 29 Jul 2002 15:57:18 -0400 (EDT) [thread overview]
Message-ID: <200207291957.g6TJvIl158896@saturn.cs.uml.edu> (raw)
In-Reply-To: <Pine.LNX.3.96.1020729074834.30577B-100000@gatekeeper.tmr.com> from "Bill Davidsen" at Jul 29, 2002 07:50:04 AM
Bill Davidsen writes:
> On Fri, 26 Jul 2002, Albert D. Cahalan wrote:
>> Jens Schmidt writes:
>>> I am not a "morse" guy myself, but appreciate this idea.
>>
>> Yeah, same here. I have to wonder if morse is the
>> best encoding, since many people don't know it.
>> The vast majority of us would need a microphone and
>> translator program anyway, so a computer-friendly
>> encoding makes more sense. Modems don't do morse.
>
> What other widely known encoding for blinking lights did you have in mind.
> Clearly there are more people who know morse than any other encoding you
> could make up, and even those who don't know it would know what it is.
ROTFL
This is NOT morse over blinking lights. Even at 12 WPM,
which is moderately fast, you'd have to stare at the
lights for over an hour without blinking! Keep in mind
that people know morse by sound, not sight, so you'd
have to slow it down. Maybe 24 hours for an oops?
(note: in morse, hex digits are slow)
No, the lights just blink. Encoding just the instruction
pointer, in binary, might be worthwhile. I have doubts.
As for the audio... you can copy morse for over an hour
or you can tape record 4 minutes of noise. Hard choice?
next prev parent reply other threads:[~2002-07-29 19:55 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-19 5:13 [PATCH -ac] Panicking in morse code Andrew Rodland
2002-07-19 5:29 ` William Lee Irwin III
2002-07-19 16:36 ` Thorsten Kranzkowski
2002-07-19 17:00 ` Andrew Rodland
2002-07-19 17:27 ` Eli Carter
2002-07-19 17:32 ` Andrew Rodland
2002-07-19 23:02 ` [PATCH -ac] Panicking in morse code, v2 Andrew Rodland
2002-07-20 10:58 ` Daniel Phillips
2002-07-20 11:19 ` Thunder from the hill
2002-07-20 13:22 ` Ville Herva
2002-07-20 14:18 ` Daniel Phillips
2002-07-20 14:55 ` Tomas Szepe
2002-07-20 16:05 ` Daniel Phillips
2002-07-20 19:51 ` Thunder from the hill
2002-07-20 0:35 ` [PATCH -ac] Panicking in morse code Alan Cox
2002-07-20 0:39 ` Andrew Rodland
2002-07-20 0:48 ` Thunder from the hill
2002-07-25 12:51 ` Bill Davidsen
2002-07-26 3:43 ` Daniel Phillips
2002-07-26 4:47 ` Daniel Phillips
2002-07-26 4:52 ` jdow
2002-07-26 5:13 ` Daniel Phillips
2002-07-26 13:50 ` Bill Davidsen
2002-07-26 13:38 ` Bill Davidsen
2002-07-26 14:39 ` Richard B. Johnson
2002-07-26 20:09 ` Bill Davidsen
2002-07-26 23:25 ` Jens Schmidt
2002-07-27 2:05 ` Albert D. Cahalan
2002-07-27 4:00 ` Andrew Rodland
[not found] ` <200207270526.g6R5Qw942780@saturn.cs.uml.edu>
2002-07-27 5:57 ` Speaker twiddling [was: Re: Panicking in morse code] Andrew Rodland
2002-07-27 9:46 ` Daniel Phillips
2002-07-27 12:57 ` David D. Hagood
2002-07-27 15:45 ` Andrew Rodland
2002-07-29 17:47 ` Pavel Machek
2002-07-29 22:02 ` Ray Friess
2002-07-29 17:49 ` Pavel Machek
2002-07-29 20:35 ` Albert D. Cahalan
2002-07-29 21:08 ` Pavel Machek
2002-07-27 18:56 ` Albert D. Cahalan
2002-07-27 19:44 ` Ville Herva
2002-07-27 22:40 ` Alan Cox
2002-07-27 21:35 ` Ville Herva
2002-07-31 15:20 ` Thunder from the hill
2002-07-27 21:40 ` Ryan Anderson
2002-07-28 10:26 ` Lars Magne Ingebrigtsen
2002-07-29 20:03 ` Albert D. Cahalan
2002-08-13 17:20 ` Mark H. Wood
2002-07-27 4:04 ` [PATCH -ac] Panicking in morse code Andrew Rodland
2002-07-29 11:50 ` Bill Davidsen
2002-07-29 12:34 ` Richard B. Johnson
2002-07-29 19:57 ` Albert D. Cahalan [this message]
2002-07-31 17:54 ` Bill Davidsen
2002-07-20 21:32 ` [PATCH -ac] Panicking in morse code v3 Andrew Rodland
2002-07-21 8:49 ` Brad Hards
2002-07-21 9:08 ` Russell King
2002-07-21 10:50 ` Zwane Mwaikambo
2002-07-21 15:43 ` Daniel Phillips
2002-07-22 17:18 ` Andrew Rodland
[not found] <20020719011300.548d72d5.arodland@noln.com.suse.lists.linux.kernel>
2002-07-19 10:38 ` [PATCH -ac] Panicking in morse code Andi Kleen
2002-07-20 7:05 ` Ville Herva
2002-07-20 11:49 ` Neale Banks
2002-07-20 11:55 ` Thunder from the hill
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=200207291957.g6TJvIl158896@saturn.cs.uml.edu \
--to=acahalan@cs.uml.edu \
--cc=arodland@noln.com \
--cc=davidsen@tmr.com \
--cc=j.schmidt@paradise.net.nz \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@arcor.de \
--cc=root@chaos.analogic.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).