From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Cc: "Lavrentiev, Anton (NIH/NLM/NCBI) [C]" <lavr@ncbi.nlm.nih.gov>
Subject: Re: SMBFS mount's file cannot be made executable
Date: Fri, 8 Nov 2024 20:51:09 +0900 [thread overview]
Message-ID: <20241108205109.55f99e2d172b9fc87e92ae67@nifty.ne.jp> (raw)
In-Reply-To: <BL0PR0901MB430827F1A0668E468B498FBBA5D70@BL0PR0901MB4308.namprd09.prod.outlook.com>
Hi all,
On Thu, 8 Aug 2019 15:41:55 +0000
"Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote:
> Hi,
>
> Here's the situation, I have a netmount "Z:" but I cannot make any files on it executable from Cygwin:
>
> $ mount
> ...
> Z: on /cygdrive/z type smbfs (binary,posix=0,user,noumount,auto)
>
> $ cd /cygdrive/z
>
> $ pwd
> /cygdrive/z
>
> $ cat a.c
> #include <stdio.h>
>
> int main()
> {
> printf("Hello world!\n");
> return 0;
> }
>
> $ gcc -Wall a.c
>
> $ echo $?
> 0
>
> $ ./a.exe
> -bash: ./a.exe: Permission denied
>
> $ ls -l a.exe
> -rw-rw-r--+ 1 lavr cppcore 157753 Aug 8 11:29 a.exe
>
> $ getfacl.exe a.exe
> # file: a.exe
> # owner: lavr
> # group: cppcore
> user::rw-
> user:lavr:rw-
> group::r--
> group:cppcore:r--
> mask::rw-
> other::r--
>
> $ chmod a+x a.exe
>
> $ echo $?
> 0
>
> $ ls -l a.exe
> -rw-rw-r--+ 1 lavr cppcore 157753 Aug 8 11:29 a.exe
>
> $ getfacl.exe a.exe
> # file: a.exe
> # owner: lavr
> # group: cppcore
> user::rw-
> user:lavr:rw-
> group::r--
> group:cppcore:r--
> mask::rw-
> other::r--
>
> $ ./a.exe
> -bash: ./a.exe: Permission denied
>
> What's missing? How to make the file executable, and why chmod() lies about all-good when it does nothing?
> Any ideas please?
>
> Thanks!
>
> P.S. I have another netmount "drive" (U:) which Cygwin identifies as "netapp", and everything works on that drive,
> regarding the execution permission.
>
> U: on /cygdrive/u type netapp (binary,posix=0,user,noumount,auto)
>
> Also, any file that I give the "x" permission from outside Cygwin (e.g. from Linux) on the SMBFS drive "Z:",
> becomes executable:
>
> Cygwin> $ gcc -Wall a.c
>
> Linux> $ chmod a+x a.exe
>
> Cygwin> $ ./a.exe
> Hello world!
Does anyone know what was the conclusion of this issue?
I have encountered the same issue and cannot find the
solution so far.
--
Takashi Yano <takashi.yano@nifty.ne.jp>
next prev parent reply other threads:[~2024-11-08 11:51 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-08 15:42 Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin
2024-11-08 11:51 ` Takashi Yano [this message]
2024-11-08 13:11 ` Corinna Vinschen
2024-11-11 10:31 ` Takashi Yano
2024-11-11 10:31 ` Takashi Yano via Cygwin
2024-11-11 10:56 ` Corinna Vinschen
2024-11-11 10:56 ` Corinna Vinschen via Cygwin
2024-11-11 11:19 ` Takashi Yano
2024-11-11 11:19 ` Takashi Yano via Cygwin
2024-11-11 11:32 ` Takashi Yano
2024-11-11 11:32 ` Takashi Yano via Cygwin
2024-11-11 11:40 ` Takashi Yano
2024-11-11 11:40 ` Takashi Yano via Cygwin
2024-11-11 12:03 ` Corinna Vinschen
2024-11-11 12:03 ` Corinna Vinschen via Cygwin
2024-11-11 12:19 ` Takashi Yano
2024-11-11 12:19 ` Takashi Yano via Cygwin
2024-11-11 13:35 ` Corinna Vinschen
2024-11-11 13:35 ` Corinna Vinschen via Cygwin
2024-11-11 19:29 ` Takashi Yano
2024-11-11 19:29 ` Takashi Yano via Cygwin
2024-11-12 8:54 ` Takashi Yano
2024-11-12 11:56 ` Corinna Vinschen
2024-11-13 9:17 ` Takashi Yano
2024-11-13 15:10 ` Bill Stewart
2024-11-13 15:37 ` Takashi Yano
2024-11-13 15:58 ` Bill Stewart
2024-11-13 16:08 ` Takashi Yano
2024-11-15 15:21 ` Takashi Yano
2024-11-18 16:26 ` Corinna Vinschen
2024-11-19 8:58 ` Takashi Yano
2024-11-19 20:54 ` Corinna Vinschen
2024-12-07 23:13 ` Takashi Yano
2024-12-08 7:57 ` Takashi Yano
2024-12-09 11:11 ` Corinna Vinschen
2024-11-12 11:31 ` Corinna Vinschen
2024-11-11 11:51 ` Takashi Yano
2024-11-11 11:51 ` Takashi Yano via Cygwin
2024-11-11 11:59 ` Corinna Vinschen
2024-11-11 11:59 ` Corinna Vinschen via Cygwin
2024-11-11 12:25 ` Takashi Yano
2024-11-11 12:25 ` Takashi Yano via Cygwin
2024-11-11 13:00 ` Takashi Yano
2024-11-11 13:00 ` Takashi Yano via Cygwin
2024-11-11 13:18 ` Corinna Vinschen
2024-11-11 13:18 ` Corinna Vinschen via Cygwin
2024-11-08 16:07 ` [EXTERNAL] " Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2024-11-11 9:04 ` Takashi Yano
2024-11-11 9:04 ` Takashi Yano via Cygwin
2019-08-12 19:05 Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin
2019-08-13 8:28 ` KAVALAGIOS Panagiotis (EEAS-EXT)
[not found] ` <704986a5a4ab41709eb963dcd23887b1@BELBRU-EXMP101.eeas.europa.eu>
2019-08-13 12:27 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin
2019-08-13 18:34 ` Achim Gratz
2019-08-13 18:35 ` Andrey Repin
2019-08-13 23:19 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin
2019-08-14 20:05 ` Andrey Repin
2019-08-14 0:53 Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin
2019-08-14 2:36 ` Ken Brown
2019-08-14 16:59 ` Achim Gratz
2019-08-14 4:24 Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin
2019-08-14 11:22 ` Ken Brown
2019-08-14 22:58 ` Brian Inglis
2019-08-14 14:07 Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin
2019-08-15 1:28 ` Ken Brown
2019-08-14 20:39 Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin
2019-08-15 1:31 ` Ken Brown
2019-08-15 1:40 Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin
2019-08-15 2:59 ` Brian Inglis
2019-08-15 2:00 Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin
2019-08-15 9:21 ` L A Walsh
2019-08-15 9:23 ` L A Walsh
2019-08-21 7:12 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin
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=20241108205109.55f99e2d172b9fc87e92ae67@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--cc=cygwin@cygwin.com \
--cc=lavr@ncbi.nlm.nih.gov \
/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).