Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
Message-ID: <E94FF01DFF6CD31186F4080009DC361501BDC868@nttwr2.tower.bldgs.butlermfg.org>
From: "Parker, Ron" <rdparker AT butlermfg DOT com>
To: Robert Collins <robert DOT collins AT itdomain DOT com DOT au>,
        Egor Duda
	 <cygwin-developers AT cygwin DOT com>
Cc: cygwin-developers AT cygwin DOT com
Subject: RE: setup will have to wait :[
Date: Mon, 26 Mar 2001 13:19:13 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"

> Right, so _how do we pass the fd_ to the child process? I'll look into
> spawn and fork. Worst case though: fifos are cygwin only. Best case I
> find some way of tricking the OS into loading up the cygwin code and
> writing "through it". Hmm I wonder if an IFS could do this (How much
> work did I think this was going to be ?!).

An IFS could do it, but the last time I checked the API and documentation
were under an NDA.