From: Derek Fawcus <dfawcus@cisco.com>
To: "André Braga" <meianoite@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] new feature: attach a process to emulated serial port
Date: Mon, 11 Oct 2004 16:47:22 +0100 [thread overview]
Message-ID: <20041011164722.I1087@edinburgh.cisco.com> (raw)
In-Reply-To: <2ad73a0410110822151a58fc@mail.gmail.com>; from meianoite@gmail.com on Mon, Oct 11, 2004 at 12:22:37PM -0300
On Mon, Oct 11, 2004 at 12:22:37PM -0300, André Braga wrote:
> On Mon, 11 Oct 2004 14:26:30 +0100, Derek Fawcus <dfawcus@cisco.com> wrote:
> > Hmm. How about simply using FIFO's instead, then one doesn't have any
> > issues with fork/system/etc
> >
> > i.e. add options of -serialin <path> -serialout <path> and have -serial <path>
> > set both of the above. Then one can simply do:
> >
> > mkfifo /tmp/serin /tmp/serout
> > anycmd < /tmp/serout > /tmp/serin &
> > qemu ... -serialin /tmp/serin -serialout /tmp/serialout
>
> That would make this feature available only on operating systems that
> support user-created named pipes.
Yeah - but they're the only interesting ones :-) Hmm is it so easy
to connect process with a bi-dir like pipe on Windows (NT) machines?
> IOW, named pipes do exist on Windows, but they're not easy to access by the user.
Hmm - SFU? The recent versions (w2k/xp only) are supposed to be very unix
like, but even the earlier version would probably support fifo's well enougth.
Mind - connecting the GUI on the earlier versions would be difficult.
> Forking is a more universal approach, as I see it.
Modulo the above proviso? Is there the ability to create "proper" pipes between
processes on NT from native win32 code?
DF
next prev parent reply other threads:[~2004-10-11 15:55 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 [this message]
2004-10-11 16:03 ` André Braga
2004-10-11 20:32 ` Johannes Martin
2004-10-11 21:38 ` Derek Fawcus
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=20041011164722.I1087@edinburgh.cisco.com \
--to=dfawcus@cisco.com \
--cc=meianoite@gmail.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).