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
Date:	Tue, 27 Mar 2001 23:32:51 -0500
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	cygwin-developers AT cygwin DOT com
Subject:	Re: mkfifo export
Message-ID:	<20010327233251.A29608@redhat.com>
Reply-To:	cygwin-developers AT cygwin DOT com
Mail-Followup-To:	cygwin-developers AT cygwin DOT com
References:	<012201c0b6b1$6b2afd60$0200a8c0 AT lifelesswks>
Mime-Version:	1.0
User-Agent:	Mutt/1.3.11i
In-Reply-To:	<012201c0b6b1$6b2afd60$0200a8c0@lifelesswks>; from robert.collins@itdomain.com.au on Tue, Mar 27, 2001 at 09:31:06PM +1000

On Tue, Mar 27, 2001 at 09:31:06PM +1000, Robert Collins wrote:
>Chris,
>    I have a basic mkfifo exported that just returns ENOSYS... Would you
>like a trivial patch to get that into cygwin - so that the next release
>of fileutils will actually try to call it rather than mknod? (I've tried
>building fileutils and it finds the mkfifo..
>
>Or would you rather wait for the whole thing? I plan to fix mknod up to
>the extent that it can create fifo's too, so fileutils probably doesn't
>_need_ a re-release.

Hmm.  I guess exporting a mkfifo that does nothing is ok for now.

cgf

- Raw text -