X-Recipient: archive-cygwin AT delorie DOT com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 7B0D738582BC
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1693222990;
	bh=S8TGXI+Lf4ikyOAIv4Ko+1Ab4++8R5ZrLS7dtWT7nDc=;
	h=References:In-Reply-To:Date:Subject:To:Cc:List-Id:
	 List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe:
	 From:Reply-To:From;
	b=QQ8q7lT4VqJErTILKoU3EQxsuTeCj5l1lpE87ieS9RUi9AsF2imMnEcf6eaTISNxX
	 fqo3DnK4FkCBJ2QFG+DnEYns9MIRbrjZNEU/YTXDRoHKJfLZQgVK9YFS7/7o4asFBW
	 BUbV3im6iD+Sm5wi3+XPku4QOEfW2Z3GPb/22iVk=
X-Original-To: cygwin AT cygwin DOT com
Delivered-To: cygwin AT cygwin DOT com
DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 1223D3858C36
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20221208; t=1693222906; x=1693827706;
 h=content-transfer-encoding:cc:to:subject:message-id:date:from
 :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc
 :subject:date:message-id:reply-to;
 bh=MD/tqxp9aW7rMhv3ND9xU5YDex9V2/WC3hELlDKUMP4=;
 b=QbpJhsSZW1T5Q+QPmSeLl0By27x8+6v3KM1xk8ptIIa/cKsJOIjrLmWs/28snYHcax
 FKLSq6hXxZ9jF4mp6QsD1pVjrrMQNE6Crk40r2ToRp2whnbfzHXpvk1Z2YhNjP5rnlbE
 TzHOlNg9T0Un+lTJzcfkDLbo2HxsiY8jWhaOLD4G7Zvu4U4Wj8Ss1IyUFUk7MM3guoW9
 c95eu2sbwQFKikM0xLzMUYzLUFEeEMAObFJEIEu8cZXfMksM1ludwmmf9XeM2zGwVldm
 0afT3IuhbbXF5Y1XuXUUiYwl61QO1uP+OoYc3Y5G48BvFliUOLKDPkQFZGqau5Ra2YRx
 L4zA==
X-Gm-Message-State: AOJu0YzdoGFwGu27dX9/ZA5hFncU6rrYX5Z9o7QtW02FFn6e09TF8q85
 8HOeax7HX7NH9FEfpVRWDucR2ThKLadEMN8yi0KFUFZx
X-Google-Smtp-Source: AGHT+IHM/pUk4c4q6p4aGjCmtEe0dFx1w4aXet2i+R8Co6Rvqi4Qf2JOeRMjRVfQcW5JRQzvOaKKBXPrS4Dm5+4ZeiI=
X-Received: by 2002:a05:6871:14a:b0:1ba:d044:8a4 with SMTP id
 z10-20020a056871014a00b001bad04408a4mr12647460oab.18.1693222906078; Mon, 28
 Aug 2023 04:41:46 -0700 (PDT)
MIME-Version: 1.0
References: <CANH4o6O-8O-iMaHowDuy0y7H=pVfZ-3EvubDmTdjGVSST8FkAQ AT mail DOT gmail DOT com>
 <CANH4o6MnH7gWj7d0vmkhCL5N0BTbkrbtGZGtso43MVZBJLBGtw AT mail DOT gmail DOT com>
 <ZN8tK/mATx6KbQWk AT calimero DOT vinschen DOT de>
 <CALXu0UcByeJHfBWSPEZkmfMqSKkmRT_5ZkxLc25EyhJzN9FUtA AT mail DOT gmail DOT com>
 <ZOMiYcQfb7i8Kc8i AT calimero DOT vinschen DOT de>
 <DM8PR09MB70950FABA8C4DAD80B0EA189A51FA AT DM8PR09MB7095 DOT namprd09 DOT prod DOT outlook DOT com>
 <CAKAoaQkPovkZhVVnkDB3wXKdHejqwKmG7vG38rfy2rtjsGV-uQ AT mail DOT gmail DOT com>
 <ZOicD/nxECrAPnKV AT calimero DOT vinschen DOT de>
 <CANH4o6Mo3yTteiQejaEaVnUQrJEAXh5N4fxKoPQHjtgr-dnC8Q AT mail DOT gmail DOT com>
 <ZOtDA3PzlR/Dk8gJ AT calimero DOT vinschen DOT de>
In-Reply-To: <ZOtDA3PzlR/Dk8gJ@calimero.vinschen.de>
Date: Mon, 28 Aug 2023 13:41:00 +0200
Message-ID: <CAEEMktO=znAQuBMLQJZ8-6r7Khft3rDG+8qYG3pqWe1dNZJAWw@mail.gmail.com>
Subject: Re: Documenting Cygwin on NFS, no longer only exchange-medium! Re:
 How to fix |mkfifo()| failure if |pathname| is on NFS ? / was: Re: [EXTERNAL]
 Re: mkfifo: cannot set permissions of 'x.fifo': Not a directory
To: cygwin AT cygwin DOT com
Cc: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
X-Spam-Status: No, score=-0.6 required=5.0 tests=BAYES_00, DKIM_SIGNED,
 DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, PLING_QUERY,
 RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS,
 TXREP autolearn=ham autolearn_force=no version=3.4.6
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on
 server2.sourceware.org
X-BeenThere: cygwin AT cygwin DOT com
X-Mailman-Version: 2.1.30
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe: <https://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From: Joshuah Hurst via Cygwin <cygwin AT cygwin DOT com>
Reply-To: Joshuah Hurst <joshhurst AT gmail DOT com>
Content-Type: text/plain; charset="utf-8"
Sender: "Cygwin" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by delorie.com id 37SBhCqq016261

On Sun, Aug 27, 2023 at 2:35 PM Corinna Vinschen via Cygwin
<cygwin AT cygwin DOT com> wrote:
>
> On Aug 26 19:44, Martin Wege via Cygwin wrote:
> > On Fri, Aug 25, 2023 at 2:19 PM Corinna Vinschen via Cygwin
> > <cygwin AT cygwin DOT com> wrote:
> > >
> > > On Aug 23 01:05, Roland Mainz via Cygwin wrote:
> > > > Note that Cygwin does not interpret the file |myfifo.fifo| as FIFO,
> > > > instead it comes back as a symlink "myfifo.fifo -> ':\0:c4:1000'".
> > > >
> > > > AFAIK there are (at least) these two options to fix the problems:
> > > > 1. Check whether the filesystem for the fifos path is NFS
> > > > (cgywin.dll's |fs.fs_is_nfs()|), and if it is a symlink check if it
> > > > starts with ':\0:c4:' (assuming "c4" is the prefix for inodes created
> > > > with |mkfifo()|). If this condition is |true|, then cygwin |stat()|,
> > > > |open()| etc. should treat this inode as FIFO.
> > >
> > > The downside is that it is not possible to diffentiate between Cygwin
> > > FIFOs and real FIFOs created from the remote side in `ls -l'
> > > output.  Note that Cygwin returns the NFS stat info verbatim, so
> > > a real FIFO is returned as a real FIFO:
> > >
> > >   linux$ mkfifo bar
> > >   cygwin$ ls -l bar
> > >   prw-r--r-- 1 corinna vinschen  0 Aug 25 13:58 bar
> > >
> > > The idea was always to use NFS as exchange medium, but not as
> > > installation medium for the entire distro or to keep Cygwin home
> > > dirs on NFS.  There were times where NFS was pretty unstable.
> > > I used NFS for quite some time to build Cygwin packages, but at one
> > > point I got trouble (performance problems with multiple concurrent
> > > processes accessing an NFS share, build errors out of the blue),
> > > so I switched to Samba shares, albeit grudgingly.  I'm not yet
> > > sure if the problems are fixed.  At least a recent OpenSSH build
> > > ran through without problems...
> >
> > Corinna, could you please update the Cygwin documentation then? We use
> > NFS, both Windows builtin and CITI NFSv4.1, with Cygwin for years
> > without major problems, so that comment about exchange-medium-only is
> > clearly wrong!
>
> I'm talking about the idea how users would use NFS, and the idea was
> that nobody in their right mind would use a crippled filesystem (from
> the Windows POV) for the entire installation.  Before you came up with
> your complaints, nobody here even knew that somebody actually did that.
>
> NFS is a niche filesystem on Windows and was never in the focus of
> anybody here, except me, because I was toying around with it and was
> happy to have it working.  As far as I knew until a few days ago,
> I was the only user of Cygwin's NFS support.
>
> As for FIFOs on NFS, as I wrote, they never worked as desired on NFS.
> For kicks I tried back until Cygwin 3.3.  Given this isn't a regression,
> it won't be fixed for Cygwin 3.4.
>
> As Brian wrote in his reply to your mail, we are all volunteers here.
> Everybody working on Cygwin is working in their spare time and/or on the
> goodwill of their employer.
>
> Cygwin is open source.  You can fix or implement stuff yourself and send
> the patches to the cygwin-patches ML for review.  Otherwise you will
> have to let us, the people actually working on the project, decide when
> and how something gets implemented.
>
> Having said that, I have a local patch enabling FIFOs on NFS.  I might
> push it at one point to the main branch, but the pressure you guys are
> currently building up on this mailing list puts me right off.

Corinna, please do not let people put you off. I don't even think it
was intended as pressure.

Could you please share the patch for testing?
-- 
Josh

-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple