Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-Id: <5.2.0.9.2.20030224155949.02e3ba88@pop3.cris.com>
X-Sender: rrschulz AT pop3 DOT cris DOT com
Date: Mon, 24 Feb 2003 16:03:12 -0800
To: cygwin AT cygwin DOT com
From: Randall R Schulz <rrschulz AT cris DOT com>
Subject: Re: mknod implementation clarification...thanks for the help
In-Reply-To: <OF4DA3607F.ADF7DB7B-ON88256CD7.007EB820@hughes.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

James,

As I guessed, the point is to create a named pipe (a.k.a. "fifo").

Here's what you need to (but doubtless do not want to) know:

At 01:15 2002-11-12, Corinna Vinschen wrote:
>On Tue, Nov 12, 2002 at 10:00:44AM +0100, Marcos Lorenzo wrote:
> > I have a backup script that uses mkfifo. Obviously it is ported from a
> > LinBox and I wanted to use it on cygwin.
>
>It won't help since there are no named pipes (yet) in Cygwin.
>
>Corinna
>
>--
>Corinna Vinschen                  Please, send mails regarding Cygwin to
>Cygwin Developer                                mailto:cygwin AT cygwin DOT com
>Red Hat, Inc.


Randall Schulz


At 15:13 2003-02-24, james DOT m DOT barker AT boeing DOT com wrote:
>Here's the sample code that calls mknod.  I always do a bad job of 
>explaining in words what I'm trying to accomplish. Hopefully the 
>sample code does a better job of it.  I'm glad to hear that plans are 
>in the work to include this capability.
>
>A series of "write" commands are made to gvFD to communicate with geomview.
>
>Thanks again
>
>Jim Barker


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/