From: Martin Wege <martin.l.wege@gmail.com>
To: cygwin@cygwin.com, Brian Inglis <Brian.Inglis@shaw.ca>,
Martin Wege <martin.l.wege@gmail.com>,
Corinna Vinschen <corinna-cygwin@cygwin.com>
Subject: Re: mkfifo: cannot set permissions of 'x.fifo': Not a directory
Date: Mon, 7 Aug 2023 23:14:43 +0200 [thread overview]
Message-ID: <CANH4o6P2fBmxvOZKVrrxDuMByHEMgs2qg14p710aUuLsFYG4rA@mail.gmail.com> (raw)
In-Reply-To: <ZNFCjtiVOhpRYhHI@calimero.vinschen.de>
On Mon, Aug 7, 2023 at 9:14 PM Corinna Vinschen
<corinna-cygwin@cygwin.com> 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
Secondly, how are fifos, other device nodes and mknod implemented? You
encode them as softlinks on ntfs? What about Windows native NFSv3
driver, do you use native mknod then to create a fifo? Where can I
find the code in cygwin for that?
Thanks,
Martin
next prev parent reply other threads:[~2023-08-07 21:14 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 14:42 Martin Wege
2023-08-07 18:26 ` Brian Inglis
2023-08-07 19:14 ` Corinna Vinschen
2023-08-07 21:14 ` Martin Wege [this message]
2023-08-08 8:20 ` Corinna Vinschen
2023-08-08 19:38 ` Martin Wege
2023-08-09 8:01 ` Corinna Vinschen
2023-08-09 9:12 ` Martin Wege
2023-08-09 9:56 ` Corinna Vinschen
2023-08-10 12:49 ` Martin Wege
2023-08-18 4:02 ` Martin Wege
2023-08-18 8:34 ` Corinna Vinschen
2023-08-18 13:14 ` Martin Wege
2023-08-21 4:49 ` Cedric Blancher
2023-08-21 8:37 ` Corinna Vinschen
2023-08-22 14:52 ` [EXTERNAL] " Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2023-08-22 23:05 ` How to fix |mkfifo()| failure if |pathname| is on NFS ? / was: " Roland Mainz
2023-08-24 16:45 ` Martin Wege
2023-08-25 4:25 ` Cedric Blancher
2023-08-26 17:58 ` Martin Wege
2023-08-25 12:18 ` Corinna Vinschen
2023-08-25 12:25 ` Corinna Vinschen
2023-08-26 11:26 ` Cedric Blancher
2023-08-26 14:15 ` Corinna Vinschen
2023-08-26 17:40 ` Martin Wege
2023-08-26 19:16 ` Brian Inglis
2023-08-25 15:14 ` Roland Mainz
2023-08-26 11:27 ` Cedric Blancher
2023-08-25 23:21 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2023-08-26 14:28 ` Corinna Vinschen
2023-08-26 14:39 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2023-08-26 17:44 ` Documenting Cygwin on NFS, no longer only exchange-medium! " Martin Wege
2023-08-26 19:16 ` Brian Inglis
2023-08-27 12:35 ` Corinna Vinschen
2023-08-28 5:35 ` Cedric Blancher
2023-08-28 10:02 ` Corinna Vinschen
2023-08-28 11:41 ` Joshuah Hurst
[not found] ` <14a692f6-7244-4a7e-a69b-d14521fb01e8@secure-endpoints.com>
2023-08-23 17:39 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2023-08-24 5:28 ` Cedric Blancher
2023-08-24 16:40 ` Martin Wege
2023-08-21 12:12 ` Martin Wege
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CANH4o6P2fBmxvOZKVrrxDuMByHEMgs2qg14p710aUuLsFYG4rA@mail.gmail.com \
--to=martin.l.wege@gmail.com \
--cc=Brian.Inglis@shaw.ca \
--cc=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).