DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:reply-to:to:subject:date:message-id
	:references:in-reply-to:content-type:content-transfer-encoding
	:mime-version; q=dns; s=default; b=XJG1qntt+zaZjVAxOTKVIZLlhvcLJ
	owPSzB3RWpde5ERHiqejD83Qc8ZJrt9xgQRe7vuZkyihUdb7O6RlxW/emzLQpkj2
	ZSJchUPIYUL2OQCxjKsErcCwfV7dXdHT9VXr8ydzkUrY/rm9YzO2uMrGQ9qx1tV9
	OlJJTPhikWV3Lg=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
IronPort-SDR: V4yZqLf95T1tWDjDAn9nKCQPiMeEpNWq5xlInPcMEUOH1pl+ZNnMGNLed4EI8lfiTX87BN1Ja7 pOgBLXghryuw==
From: "Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin" <cygwin AT cygwin DOT com>
Reply-To: "Lavrentiev, Anton (NIH/NLM/NCBI) [C]" <lavr AT ncbi DOT nlm DOT nih DOT gov>
To: "'cygwin AT cygwin DOT com'" <cygwin AT cygwin DOT com>
Subject: RE: SMBFS mount's file cannot be made executable
Date: Tue, 13 Aug 2019 12:27:16 +0000
Message-ID: <BN6PR09MB1409D5E76638A6D39C8ED13FA5D20@BN6PR09MB1409.namprd09.prod.outlook.com>
References: <BN6PR09MB1409EACEBA48577B4C6CC3D2A5D30 AT BN6PR09MB1409 DOT namprd09 DOT prod DOT outlook DOT com> <704986a5a4ab41709eb963dcd23887b1 AT BELBRU-EXMP101 DOT eeas DOT europa DOT eu>
In-Reply-To: <704986a5a4ab41709eb963dcd23887b1@BELBRU-EXMP101.eeas.europa.eu>
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-userprincipalname: s7gpKpUGIC8ZeWjK4K1XG7LSiTUuH5rqLr+u4KgrvtUtDvzF5deAwnB1NsA9gBPW
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id x7DCS0OU009107

Thanks for responding!

> You need the "exec" mount option.

I thought so too, but how do I give that option to a drive that is "noumount".  I cannot dis- or re-mount it AFAICT.

$ mount
...
Z: on /cygdrive/z type smbfs (binary,posix=0,user,noumount,auto)
$ umount /cygdrive/z
umount: /cygdrive/z: Invalid argument

Also, I tried to mount the same path elsewhere, and with the "exec" options, and that wouldn't help, either:

$ mount -o exec //coredev2/home/lavr /mnt
$ mount
//coredev2/home/lavr on /mnt type smbfs (binary,exec,user)
...
$ cd /mnt
$ pwd
/mnt
$ gcc a.c
$ ls -l a.exe
-rw-rw-r--+ 1 lavr cppcore 157753 Aug 13 08:20 a.exe
$ ./a.exe
-bash: ./a.exe: Permission denied
(and again, if a.exe is given the "x" perm in the Linux fs, the command above works)

I think that something's wrong with how (or if) Cygwin translates the "x" unix execution permission bit to an ACL that is passed thru SMB -- it does not get transferred to the Linux side correctly.  But if set there, then it gets converted to the execute ACL the right way, and that makes the file executable on the Windows side...  I do not know how is it all implemented, though;  it's just my observation.


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