From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1FHKYT-000082-RM
	for qemu-devel@nongnu.org; Thu, 09 Mar 2006 07:47:46 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1FHKYP-00005k-5P
	for qemu-devel@nongnu.org; Thu, 09 Mar 2006 07:47:44 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1FHKYO-00005b-S3
	for qemu-devel@nongnu.org; Thu, 09 Mar 2006 07:47:40 -0500
Received: from [65.75.192.11] (helo=mail.ipinc.net)
	by monty-python.gnu.org with esmtp (Exim 4.52) id 1FHKbS-0002PH-Mu
	for qemu-devel@nongnu.org; Thu, 09 Mar 2006 07:50:51 -0500
From: wanderer@ipinc.net
Subject: Re: [Qemu-devel] [PATCH] Remote console access though socket
MIME-Version: 1.0
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200603090300.13378.wanderer@ipinc.net>
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
Date: Thu, 09 Mar 2006 12:47:47 -0000
To: qemu-devel@nongnu.org
Cc: daniel@veillard.com

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.