From: Derek Fawcus <dfawcus@cisco.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] new feature: attach a process to emulated serial port
Date: Mon, 11 Oct 2004 22:38:03 +0100 [thread overview]
Message-ID: <20041011223803.B8377@edinburgh.cisco.com> (raw)
In-Reply-To: <Pine.LNX.4.56.0410112221520.2657@halef.NotaMusica.com>; from jmartin@notamusica.com on Mon, Oct 11, 2004 at 10:32:29PM +0200
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
next prev parent reply other threads:[~2004-10-11 21:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-08 21:46 [Qemu-devel] new feature: attach a process to emulated serial port Johannes Martin
2004-10-11 13:26 ` Derek Fawcus
2004-10-11 15:22 ` André Braga
2004-10-11 15:47 ` Derek Fawcus
2004-10-11 16:03 ` André Braga
2004-10-11 20:32 ` Johannes Martin
2004-10-11 21:38 ` Derek Fawcus [this message]
2004-10-11 21:47 ` Derek Fawcus
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=20041011223803.B8377@edinburgh.cisco.com \
--to=dfawcus@cisco.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).