On 09/07/15 04:30, Michael Roth wrote:
Quoting Denis V. Lunev (2015-07-08 17:47:51)
On 09/07/15 01:02, Michael Roth wrote:
Quoting Denis V. Lunev (2015-07-07 03:06:08)
On 07/07/15 04:31, Michael Roth wrote:
Quoting Denis V. Lunev (2015-06-30 05:25:19)
From: Olga Krishtal
Child process' std
Quoting Denis V. Lunev (2015-07-08 17:47:51)
> On 09/07/15 01:02, Michael Roth wrote:
> > Quoting Denis V. Lunev (2015-07-07 03:06:08)
> >> On 07/07/15 04:31, Michael Roth wrote:
> >>> Quoting Denis V. Lunev (2015-06-30 05:25:19)
> From: Olga Krishtal
>
> Child process' stdin/stdout
On 09/07/15 01:02, Michael Roth wrote:
Quoting Denis V. Lunev (2015-07-07 03:06:08)
On 07/07/15 04:31, Michael Roth wrote:
Quoting Denis V. Lunev (2015-06-30 05:25:19)
From: Olga Krishtal
Child process' stdin/stdout/stderr can be associated
with handles for communication via read/write inter
Quoting Denis V. Lunev (2015-07-07 03:06:08)
> On 07/07/15 04:31, Michael Roth wrote:
> > Quoting Denis V. Lunev (2015-06-30 05:25:19)
> >> From: Olga Krishtal
> >>
> >> Child process' stdin/stdout/stderr can be associated
> >> with handles for communication via read/write interfaces.
> >>
> >> Th
On 07/07/15 12:12, Olga Krishtal wrote:
On 07/07/15 11:06, Denis V. Lunev wrote:
On 07/07/15 04:31, Michael Roth wrote:
Quoting Denis V. Lunev (2015-06-30 05:25:19)
From: Olga Krishtal
Child process' stdin/stdout/stderr can be associated
with handles for communication via read/write interfac
On 07/07/15 12:12, Olga Krishtal wrote:
On 07/07/15 11:06, Denis V. Lunev wrote:
On 07/07/15 04:31, Michael Roth wrote:
Quoting Denis V. Lunev (2015-06-30 05:25:19)
From: Olga Krishtal
Child process' stdin/stdout/stderr can be associated
with handles for communication via read/write interfac
On 07/07/15 11:06, Denis V. Lunev wrote:
On 07/07/15 04:31, Michael Roth wrote:
Quoting Denis V. Lunev (2015-06-30 05:25:19)
From: Olga Krishtal
Child process' stdin/stdout/stderr can be associated
with handles for communication via read/write interfaces.
The workflow should be something lik
On 07/07/15 04:31, Michael Roth wrote:
Quoting Denis V. Lunev (2015-06-30 05:25:19)
From: Olga Krishtal
Child process' stdin/stdout/stderr can be associated
with handles for communication via read/write interfaces.
The workflow should be something like this:
* Open an anonymous pipe through g
Quoting Denis V. Lunev (2015-06-30 05:25:19)
> From: Olga Krishtal
>
> Child process' stdin/stdout/stderr can be associated
> with handles for communication via read/write interfaces.
>
> The workflow should be something like this:
> * Open an anonymous pipe through guest-pipe-open
> * Execute a
From: Olga Krishtal
Child process' stdin/stdout/stderr can be associated
with handles for communication via read/write interfaces.
The workflow should be something like this:
* Open an anonymous pipe through guest-pipe-open
* Execute a binary or a script in the guest. Arbitrary arguments and
e
From: Olga Krishtal
Child process' stdin/stdout/stderr can be associated
with handles for communication via read/write interfaces.
The workflow should be something like this:
* Open an anonymous pipe through guest-pipe-open
* Execute a binary or a script in the guest. Arbitrary arguments and
e
From: Olga Krishtal
Child process' stdin/stdout/stderr can be associated
with handles for communication via read/write interfaces.
The workflow should be something like this:
* Open an anonymous pipe through guest-pipe-open
* Execute a binary or a script in the guest. Arbitrary arguments and
e
12 matches
Mail list logo
