This is the mail archive of the
mailing list for the Cygwin project.
Re: cygwin permissions problem on a network drive
- From: "Larry Hall (Cygwin)" <reply-to-list-only-lh at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Tue, 02 Aug 2011 16:53:38 -0400
- Subject: Re: cygwin permissions problem on a network drive
- References: <email@example.com>
- Reply-to: cygwin at cygwin dot com
On 8/2/2011 12:10 PM, firstname.lastname@example.org 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 "noacl". If you're
accessing the share via /cygdrive, create a distinct mount point for it.
I'm not sure that I'm doing this the right way.
No. I meant a distinct mount point, *different* from your cygdrive
prefix. See http://cygwin.com/cygwin-ug-net/using.html#cygdrive
H: /h xyz binary,noacl 0 0
none /mnt cygdrive binary,posix=0,user 0 0
H: /myhome xyz binary,noacl 0 0
none / cygdrive binary,posix=0,user 0 0
I'm having the same problems with my $HOME folder, which is on a network
share. I was able to create an extra mount point for the location,
unfortunately that didn't help with the original $HOME. Could you please
describe what I have to do circumvent the permission problem for $HOME?
Access you $HOME folder through the new mount point (i.e. /h or /myhome)
and you should be all set.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple