Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com X-Authentication-Warning: bono.reversers.net: stefan owned process doing -bs Date: Wed, 13 Sep 2000 23:04:36 +0200 (CEST) From: stefan X-Sender: stefan AT bono DOT reversers DOT net To: friedman_hill ernest j cc: Cygwin Mailing List Subject: Re: ifconf In-Reply-To: <200009131312.GAA06633@california.sandia.gov> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Wed, 13 Sep 2000, friedman_hill ernest j wrote: > I have been developing named pipe support for cygwin which I hope to > submit for inclusion in a future version. I have finally gotten > my employer to sign away the rights to the code, so I will hopefully > be sharing it with the list soon. > > Note that despite the name, the semantics of UNIX FIFOs and Win32 > named pipes are completely different, so you can't use win32 named > pipes to emulate FIFOs. Yes I know. In my own port of named pipe support i wanted to make use of NT's ability to share named pipes over M$ network. But unfortunaly i ran into problems with it because there are no programs actually using that kerneld feature which could tell how to do. Another point is that named pipes cannot be used in Win9x and WinME. Anyway you'll find the symbols in kerneld. Thus you wont need different binaries... I would be *very* interested in what you have !!! stefan AT lkcc DOT org -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com