From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1CH7zS-0007vI-B5 for qemu-devel@nongnu.org; Mon, 11 Oct 2004 17:45:58 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1CH7zR-0007v2-OC for qemu-devel@nongnu.org; Mon, 11 Oct 2004 17:45:57 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CH7zR-0007uo-Io for qemu-devel@nongnu.org; Mon, 11 Oct 2004 17:45:57 -0400 Received: from [144.254.224.140] (helo=ams-iport-1.cisco.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1CH7rp-0004gE-9j for qemu-devel@nongnu.org; Mon, 11 Oct 2004 17:38:05 -0400 Received: from cisco.com (edinburgh.cisco.com [144.254.112.76]) by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i9BLc1Sf012954 for ; Mon, 11 Oct 2004 23:38:01 +0200 (MEST) Received: (from dfawcus@localhost) by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) id WAA04784 for qemu-devel@nongnu.org; Mon, 11 Oct 2004 22:38:03 +0100 (BST) Date: Mon, 11 Oct 2004 22:38:03 +0100 From: Derek Fawcus Subject: Re: [Qemu-devel] new feature: attach a process to emulated serial port Message-ID: <20041011223803.B8377@edinburgh.cisco.com> References: <20041011142629.C1087@edinburgh.cisco.com> <2ad73a0410110822151a58fc@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: ; from jmartin@notamusica.com on Mon, Oct 11, 2004 at 10:32:29PM +0200 Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On Mon, Oct 11, 2004 at 10:32:29PM +0200, Johannes Martin wrote: > Actually, that's kind of what I tried before (-serial stdio, with > stdin/stdout redirected to a pipe). However, some programs don't like > that. Most importantly, slirp doesn't work with it - it seems to expect a > real tty. Huh? I've not played with the slirp code, but why should it care? I note that the misc.c file in the slirp code can use pty's internally, but that shouldn't matter. Just what requires that a pty be used as a form of IPC to slirp? Frankly, i should be able to work with any form of byte stream. > Sorry if I have to disappoint: I'm not sure whether the forkpty() call is > available in Windoze. The -serial pty code is disabled for a Windows > compile, so I did the same for my -serial exec code. If there's a windows > guru out there who knows whether ptys are emulated in cygwin maybe you can > test whether it will work in windoze as well. The other problem with this for windows style programs is that most of them (as I understand) pay no attention to stdin/stdout. So this is a bit pointless. BTW: Just what sort of program do you fork off of the serial port? DF