All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: Chris Friesen <cfriesen@nortelnetworks.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: how to redirect serial console to telnet session?
Date: Fri, 10 May 2002 16:29:02 +0100	[thread overview]
Message-ID: <20020510162902.C7165@flint.arm.linux.org.uk> (raw)
In-Reply-To: <3CDBC5A5.A1844CC0@nortelnetworks.com> <20020510160945.B7165@flint.arm.linux.org.uk> <3CDBD9EA.1826BB48@nortelnetworks.com>

On Fri, May 10, 2002 at 10:32:10AM -0400, Chris Friesen wrote:
> I found some patches by Ingo Molnar, but they look like kernel mods.

That's the one.

> What I'm really looking for is a way to redirect this from userspace in
> a stock kernel.

There isn't anything in the stock kernel that will let you do this
without some form of patches being applied.

> I want the serial console as normal, but then for just debugging this
> one thing I want to telnet in over ethernet and basically redirect /dev/ttyS0
> onto my telnet session.

telnet (and its associated protocol) is a completely different beast to
serial consoles - in fact any network connection is.

If you really want to get at the kernel message data, there's dmesg
or a simple cat /proc/kmsg.  The problem with these is, when the kernel
crashes, you won't get the last messages.  Also, if you're generating
more than 16K of messages before allowing the kernel to continue (and
thus user space) you're also going to loose messages.

-- 
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html


  reply	other threads:[~2002-05-10 15:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-10 13:05 how to redirect serial console to telnet session? Chris Friesen
2002-05-10 15:09 ` Russell King
2002-05-10 14:32   ` Chris Friesen
2002-05-10 15:29     ` Russell King [this message]
2002-05-11 14:26     ` Denis Vlasenko
2002-05-10 15:18   ` Randy.Dunlap

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=20020510162902.C7165@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=cfriesen@nortelnetworks.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.