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 Message-ID: From: "Parker, Ron" To: cygwin-developers AT cygwin DOT com Subject: RE: setup will have to wait :[ Date: Mon, 26 Mar 2001 14:26:09 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Installable File System. Under Win3x and Win9x IFS's are used in implementing some network protocols using IFSMgr. The API was part of the DDK, but with no sample code and little documentation. Under WinNT, Win2k and Whistler the IFS development kit is ~$900US and requires a license from Microsoft. As you might expect an IFS is not interchangable between NT'ish and 95.ish > -----Original Message----- > From: Christopher Faylor [mailto:cgf AT redhat DOT com] > Sent: Monday, March 26, 2001 1:49 PM > To: Egor Duda > Subject: Re: setup will have to wait :[ > > > 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 >