Re: [PATCH -ac] Panicking in morse code

From: Bill Davidsen <davidsen@tmr.com>
To: "Albert D. Cahalan" <acahalan@cs.uml.edu>
Cc: Jens Schmidt <j.schmidt@paradise.net.nz>,
	root@chaos.analogic.com, Daniel Phillips <phillips@arcor.de>,
	Andrew Rodland <arodland@noln.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH -ac] Panicking in morse code
Date: Wed, 31 Jul 2002 13:54:29 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.3.96.1020731135028.10066C-100000@gatekeeper.tmr.com> (raw)
In-Reply-To: <200207291957.g6TJvIl158896@saturn.cs.uml.edu>

On Mon, 29 Jul 2002, Albert D. Cahalan wrote:

> Bill Davidsen writes:

> > 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)

I certainly didn't think more than the original (prime cause) message was
going to be sent, the whole oops would be useless, some "dereference NULL
pointer" might be, and even "oh shit I die now" would be pretty obvious to
anyone who knows any code at all.

-- 
bill davidsen <davidsen@tmr.com>
  CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.