Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Date: Mon, 26 Mar 2001 14:49:08 -0500 From: Christopher Faylor To: Egor Duda Subject: Re: setup will have to wait :[ Message-ID: <20010326144908.B9410@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: Egor Duda References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: ; from rdparker@butlermfg.com on Mon, Mar 26, 2001 at 01:19:13PM -0600 On Mon, Mar 26, 2001 at 01:19:13PM -0600, Parker, Ron wrote: >> 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. What is an IFS, Ron? cgf