From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 2155) id 8699C3858D33; Tue, 8 Aug 2023 08:20:44 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8699C3858D33 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1691482844; bh=gVI1B7Hkp6ekshrYaNmB9ZQTjRDEPCBuO+SOn+VVruk=; h=Date:From:To:Cc:Subject:Reply-To:References:In-Reply-To:From; b=AS67OBXCa7U2kqRfUSPp6IuxcLFcWPZbHzJdCrrjz2f72UdbfmsG4YOqcMYvl8LRc pn5/YzVx7Z20a10xxxoFqCSbEF49V/yA0IQELPFfNMjZx1+I3CCIZZ6tyM2UjOC5tU thE8K+7vvz552QYJ6jRxshMBaH2Eh9ETNuUWMgWw= Received: by calimero.vinschen.de (Postfix, from userid 500) id 2C6C1A80C3B; Tue, 8 Aug 2023 10:20:42 +0200 (CEST) Date: Tue, 8 Aug 2023 10:20:42 +0200 From: Corinna Vinschen To: Martin Wege Cc: cygwin@cygwin.com, Brian Inglis Subject: Re: mkfifo: cannot set permissions of 'x.fifo': Not a directory Message-ID: Reply-To: cygwin@cygwin.com Mail-Followup-To: Martin Wege , cygwin@cygwin.com, Brian Inglis References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: List-Id: On Aug 7 23:14, Martin Wege via Cygwin wrote: > On Mon, Aug 7, 2023 at 9:14 PM Corinna Vinschen > wrote: > > > > On Aug 7 12:26, Brian Inglis via Cygwin wrote: > > > On 2023-08-07 08:42, Martin Wege via Cygwin wrote: > > > > We get a weird mkfifo failure in Cygwin on NTFS: > > > > > > > > /usr/bin/mkfifo -m 600 x.fifo > > > > mkfifo: cannot set permissions of 'x.fifo': Not a directory > > > > > > This error is also reproducible with default fifo permissions 666 or > > > anything else, and appears to be returned by gen_full_path_at() in > > > syscalls.cc when called with a fifo: > > > > This will be fixed in 3.4.8, > > Thank you > > > see > > https://cygwin.com/git/?p=newlib-cygwin.git;a=commit;h=b56b4d7fd85b > > First, Can I download a beta of 3.4.8, or any other version with that > fix? It's pretty urgent You can install a test release of Cygwin, simply by using the setup tool These test releases are always created from the git main branch, though, so they are always test releases of the next major version, currently 3.5.0. > Secondly, how are fifos, other device nodes and mknod implemented? You > encode them as softlinks on ntfs? Not only on NTFS. FIFOs on the disk are always created as symlinks with a special target string, recognized by Cygwin. No differece on NFS. Microsoft NFSv3 has no way to specify creating a "real" FIFO on the remote filesystem. It wouldn't make sense anyway, because there's no way to share the FIFO across systems. Corinna