On Jan 4 15:25, Markus Leuthold wrote:
On Jul 5 10:59, Corinna Vinschen wrote:
On Jul 5 12:21, Bill Metzenthen wrote:
What should I ask the system administrator to change so that cygwin
will once again work on this drive? Perhaps there is some new setting
(or an old one which has
On Jul 5 10:59, Corinna Vinschen wrote:
On Jul 5 12:21, Bill Metzenthen wrote:
What should I ask the system administrator to change so that cygwin
will once again work on this drive? Perhaps there is some new setting
(or an old one which has somehow changed) for cygwin that I have
failed
On Oct 20 18:58, gds wrote:
On 10/18/2011 08:52 AM, Lemke, Michael SZ/HZA-ZSW wrote:
I know this an old thread but I am in exactly the same situation as
the OP. Access with 1.7.7 and before worked fine, 1.7.9 has this
problem. The workaround with explicit noacl option works for me but
On Friday, October 21, 2011 10:50 AM
Corinna Vinschen wrote:
On Oct 20 18:58, gds wrote:
On 10/18/2011 08:52 AM, Lemke, Michael SZ/HZA-ZSW wrote:
I know this an old thread but I am in exactly the same situation as
the OP. Access with 1.7.7 and before worked fine, 1.7.9 has this
problem.
On Oct 21 12:15, Lemke, Michael SZ/HZA-ZSW wrote:
On Friday, October 21, 2011 10:50 AM
Corinna Vinschen wrote:
On Oct 20 18:58, gds wrote:
On 10/18/2011 08:52 AM, Lemke, Michael SZ/HZA-ZSW wrote:
I know this an old thread but I am in exactly the same situation as
the OP. Access
On October 21, 2011 12:55 PM Corinna Vinschen wrote:
On Oct 21 12:15, Lemke, Michael SZ/HZA-ZSW wrote:
On Friday, October 21, 2011 10:50 AM
Corinna Vinschen wrote:
On Oct 20 18:58, gds wrote:
On 10/18/2011 08:52 AM, Lemke, Michael SZ/HZA-ZSW wrote:
I know this an old thread but I
On 10/21/2011 06:55 AM, Corinna Vinschen wrote:
On Oct 21 12:15, Lemke, Michael SZ/HZA-ZSW wrote:
On Friday, October 21, 2011 10:50 AM
Corinna Vinschen wrote:
On Oct 20 18:58, gds wrote:
On 10/18/2011 08:52 AM, Lemke, Michael SZ/HZA-ZSW wrote:
I know this an old thread but I am in
On Oct 21 16:13, Lemke, Michael SZ/HZA-ZSW wrote:
On October 21, 2011 12:55 PM Corinna Vinschen wrote:
On Oct 21 12:15, Lemke, Michael SZ/HZA-ZSW wrote:
This is by design here. IT wants it that way.
Then noacl' is the only way for you.
Unless I wait for the next release, right?
No.
On Oct 21 10:16, gds wrote:
On 10/21/2011 06:55 AM, Corinna Vinschen wrote:
On Oct 21 12:15, Lemke, Michael SZ/HZA-ZSW wrote:
On Friday, October 21, 2011 10:50 AM
Corinna Vinschen wrote:
On Oct 20 18:58, gds wrote:
On 10/18/2011 08:52 AM, Lemke, Michael SZ/HZA-ZSW wrote:
I know this
On October 21, 2011 4:36 PM Corinna Vinschen wrote:
On Oct 21 16:13, Lemke, Michael SZ/HZA-ZSW wrote:
On October 21, 2011 12:55 PM Corinna Vinschen wrote:
On Oct 21 12:15, Lemke, Michael SZ/HZA-ZSW wrote:
This is by design here. IT wants it that way.
Then noacl' is the only way for you.
On 10/21/2011 10:39 AM, Corinna Vinschen wrote:
On Oct 21 10:16, gds wrote:
On 10/21/2011 06:55 AM, Corinna Vinschen wrote:
On Oct 21 12:15, Lemke, Michael SZ/HZA-ZSW wrote:
On Friday, October 21, 2011 10:50 AM
Corinna Vinschen wrote:
On Oct 20 18:58, gds wrote:
On 10/18/2011 08:52 AM,
On Oct 21 12:32, gds wrote:
If I do chmod 000 testfile I see with ls -l:
-r--r--r--
If I do chmod 777 testfile I see
-rw-r--r--
So there is a small effect but not much.
In noacl mode or on file systems not supporting ACLs (FAT, for instance)
permissions are emulated using the DOS R/O bit
On 10/18/2011 08:52 AM, Lemke, Michael SZ/HZA-ZSW wrote:
I know this an old thread but I am in exactly the same situation as
the OP. Access with 1.7.7 and before worked fine, 1.7.9 has this
problem. The workaround with explicit noacl option works for me but
it is rather awkward as I have to
On Jul 5 10:59, Corinna Vinschen wrote:
On Jul 5 12:21, Bill Metzenthen wrote:
I have problems with permissions on a network drive. The drive is
maintained by others and I have no control over the Windows
permissions of the drive.
[...]
If I now try to use cygwin to create anything then
On Jul 6 11:43, Bill Metzenthen wrote:
Corinna Vinschen wrote:
If I now try to use cygwin to create anything then it fails (despite
it reporting that I have rwx permissions for the directory):
For now, set the mount point for this drive to noacl. If you're
accessing the share
On 8/2/2011 12:10 PM, spamboun...@gmx.de wrote:
On Jul 6 11:43, Bill Metzenthen wrote:
Corinna Vinschen wrote:
If I now try to use cygwin to create anything then it fails (despite
it reporting that I have rwx permissions for the directory):
For now, set the mount point for this drive to
On Jul 6 11:43, Bill Metzenthen wrote:
Corinna Vinschen wrote:
If I now try to use cygwin to create anything then it fails (despite
it reporting that I have rwx permissions for the directory):
For now, set the mount point for this drive to noacl. If you're
accessing the share via
On Jul 5 12:21, Bill Metzenthen wrote:
I have problems with permissions on a network drive. The drive is
maintained by others and I have no control over the Windows
permissions of the drive.
[...]
If I now try to use cygwin to create anything then it fails (despite
it reporting that I have
On Jul 5 10:59, Corinna Vinschen wrote:
On Jul 5 12:21, Bill Metzenthen wrote:
What should I ask the system administrator to change so that cygwin
will once again work on this drive? Perhaps there is some new setting
(or an old one which has somehow changed) for cygwin that I have
Corinna Vinschen wrote:
If I now try to use cygwin to create anything then it fails (despite
it reporting that I have rwx permissions for the directory):
For now, set the mount point for this drive to noacl. If you're
accessing the share via /cygdrive, create a distinct mount point for it.
I have problems with permissions on a network drive. The drive is
maintained by others and I have no control over the Windows
permissions of the drive.
I have a directory on the drive and I can use Windows Explorer to
create and write files and subdirectories to it. I can also use the
Windows
21 matches
Mail list logo
