Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 31 Jul 2002 13:59:13 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 31 Jul 2002 13:59:13 -0400 Received: from tmr-02.dsl.thebiz.net ([216.238.38.204]:4878 "EHLO gatekeeper.tmr.com") by vger.kernel.org with ESMTP id ; Wed, 31 Jul 2002 13:59:12 -0400 Date: Wed, 31 Jul 2002 13:54:29 -0400 (EDT) From: Bill Davidsen To: "Albert D. Cahalan" cc: Jens Schmidt , root@chaos.analogic.com, Daniel Phillips , Andrew Rodland , linux-kernel@vger.kernel.org Subject: Re: [PATCH -ac] Panicking in morse code In-Reply-To: <200207291957.g6TJvIl158896@saturn.cs.uml.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1264 Lines: 33 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 CTO, TMR Associates, Inc Doing interesting things with little computers since 1979. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/