From: wanderer@ipinc.net
To: qemu-devel@nongnu.org
Cc: daniel@veillard.com
Subject: Re: [Qemu-devel] [PATCH] Remote console access though socket
Date: Thu, 09 Mar 2006 12:47:47 -0000 [thread overview]
Message-ID: <200603090300.13378.wanderer@ipinc.net> (raw)
I placed a patch on The Qemu Forum (qemu.dad-answers.com) that already
provides this capability in a more inclusive manner. That is, you can remote
the console (monitor) through any active pty or pipe process. Telnet could be
one choice to get the functionality you are getting at here.
Then again, perhaps I misunderstood your code entirely. Take a look and see.
next reply other threads:[~2006-03-09 12:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-09 12:47 wanderer [this message]
2006-03-09 12:55 ` [Qemu-devel] [PATCH] Remote console access though socket Daniel Veillard
-- strict thread matches above, loose matches on Subject: below --
2006-03-08 14:52 Daniel Veillard
[not found] ` <16af12af0603081035h5f61d947y6c24b7a7675eeb14@mail.gmail.com>
2006-03-08 20:35 ` Ed Swierk
2006-03-11 20:53 ` Daniel Veillard
2006-03-11 16:24 ` Oliver Gerlich
2006-03-11 20:59 ` Daniel Veillard
2006-03-11 22:22 ` Oliver Gerlich
2006-03-12 11:03 ` Daniel Veillard
2006-03-11 21:07 ` Daniel Veillard
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=200603090300.13378.wanderer@ipinc.net \
--to=wanderer@ipinc.net \
--cc=daniel@veillard.com \
--cc=qemu-devel@nongnu.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).