linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ville Herva <vherva@niksula.hut.fi>
To: "Albert D. Cahalan" <acahalan@cs.uml.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Speaker twiddling [was: Re: Panicking in morse code]
Date: Sat, 27 Jul 2002 22:44:29 +0300	[thread overview]
Message-ID: <20020727194429.GR1548@niksula.cs.hut.fi> (raw)
In-Reply-To: <200207271856.g6RIufn63592@saturn.cs.uml.edu>

On Sat, Jul 27, 2002 at 02:56:41PM -0400, you [Albert D. Cahalan] wrote:
> Reality?
> 
> There's no "set up a microphone and decoder" problem.
> Most people have a tape recorder. Use that, then play
> back into the PC's sound card after you reboot. Post the
> sound file on a web site.

Reality?

I don't have a tape recorder, and even if I had that procedure is so tedious
that I'd rather write the oops down with a pen. And I don't use pen
willingly as it is error prone. (I don't even dare to think what Windows
people would say if I actually found a magnetophone and a mic and tried to
sneak into the curiously twittering server room without anyone noticing.)

Let's get real. There's much better solutions already available: 
 - serial console that has been in kernel for ages
   (sneaking into server room with an old laptop and serial cable
   at least _looks_ professional)
 - kmsgdump from Willy Tarreau that writes the oops to a floppy (even makes
   a msdos fs), can use printer and enables pgup/pgdown even after lockup so
   that you can see the whole kernel ring buffer (who would ever notice if
   you sneak out from the server room with a floppy or a sheet of paper)
   http://wtarreau.free.fr/kmsgdump/
 - netconsole from Ingo Molnar that logs the oops over udp (you don't even
   have to sneak into the server room)
   http://people.redhat.com/mingo/netconsole-patches/

Now, I would assume that most people have a floppy, printer or a network
connection. At least more people than have a tape recorder.


-- v --

v@iki.fi

  reply	other threads:[~2002-07-27 19:41 UTC|newest]

Thread overview: 59+ 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 [this message]
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
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] <04a801c235b9$03f699f0$1125a8c0@wednesday>
2002-07-28  0:43 ` Speaker twiddling [was: Re: Panicking in morse code] Albert D. Cahalan

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=20020727194429.GR1548@niksula.cs.hut.fi \
    --to=vherva@niksula.hut.fi \
    --cc=acahalan@cs.uml.edu \
    --cc=linux-kernel@vger.kernel.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).