Mailinglist Archive: opensuse (2835 mails)

< Previous Next >
[opensuse] How to attach to existing tty
  • From: Simon Roberts <thorpflyer@xxxxxxxxx>
  • Date: Tue, 5 Dec 2006 09:31:55 -0800 (PST)
  • Message-id: <20061205173157.34191.qmail@xxxxxxxxxxxxxxxxxxxxxxx>
Hi all,

This, I guess, is probably a generic Unix question, but in all my Unix years I've never tried to do this, and the manpages have yielded no clue where to start (at least no clue that I recognized as a clue :)

I want to attach to the output stream of an existing terminal. I want to "tee" that output to the serial device so I can send it to another machine that will log and save the output. The terminal in question is created and started by "the system". It is acutally /dev/tty10, and is receiving log messages about kernel activity.

The problem is that I'm getting a recursive kernel panic, and I want to capture it so I can report the error. This output doesn't seem to be sent to any file anywhere (so far as I can tell), which I guess is reasonable in the event of a panic, as not much of the kernel's behavior will be trustworthy. However, it seems reasonable that I might manage to ship this stuff out of a serial port.

Other option suggested was to take a photo of the screen, but the messages disappear off the top of the page (due to the recursive nature of the thing) before I can switch terminals, so this isn't a very useful option.

Come to think of it, the last time I had a kernel panic, it was under Solaris, and I used "kdb" to capture it I think (too long ago to remember clearly!) Is there a similar facility in Linux? (Solaris/kdb starts the whole darn kernel under a debugger from the OBP (forth) boot prom prompt).

Any suggestions?


"You can tell whether a man is clever by his answers. You can tell whether a man is wise by his questions." — Naguib Mahfouz

Have a burning question?
Go to and get answers from real people who know.
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx

< Previous Next >