can not mount Windows shares correctly
Larry Hall (Cygwin)
reply-to-list-only-lh@cygwin.com
Mon Nov 18 18:36:00 GMT 2013
On 11/18/2013 1:08 PM, DEWI - N. Zacharias wrote:
> Hi all,
>
> Situation : A windows shared NAS to which I can connect using
>
> net use \\\\192.168.109.252\\storage /user:PC06\\user1 passwd
>
> but then it is not possible to mount it to lets say /cygdrive/b
>
> mount \\\\192.168.109.252\\storage /cygdrive/b
>
> mount: warning - /cygdrive/s does not exist.
> mount: defaulting to 'notexec' mount option for speed since native path
> references a remote share. Use '-f' option to override.
The mount worked fine, as you can see from below.
> But
>
> $ mount
> //192.168.109.252/storage on /cygdrive/b type smbfs (binary,notexec,noacl,u=
> ser)
> C:/cygwin/bin on /usr/bin type ntfs (binary,auto) C:/cygwin/lib on /usr/lib type ntfs (binary,auto) C:/cygwin on / type ntfs (binary,auto)
> B: on /cygdrive/b type ntfs (binary,posix=3D0,user,noumount,auto)
> C: on /cygdrive/c type ntfs (binary,posix=3D0,user,noumount,auto)
> D: on /cygdrive/d type ntfs (binary,posix=3D0,user,noumount,auto)
> E: on /cygdrive/e type vfat (binary,posix=3D0,user,noumount,auto)
> F: on /cygdrive/f type ntfs (binary,posix=3D0,user,noumount,auto)
> H: on /cygdrive/h type nwfs (binary,posix=3D0,user,noumount,auto)
>
> And:
>
> $ ls -al /cygdrive/b/
> ls: cannot access /cygdrive/b/: No such file or directory
As expected, since you haven't provided the authentication necessary yet.
> If I use
>
> net use b: \\\\192.168.109.252\\storage /user:PC06\\user1 passwd The command completed successfully.
>
> The result is slightly different:
>
>
> $ mount
> //192.168.109.252/storage on /cygdrive/b type smbfs (binary,notexec,noacl,u=
> ser)
> C:/cygwin/bin on /usr/bin type ntfs (binary,auto) C:/cygwin/lib on /usr/lib type ntfs (binary,auto) C:/cygwin on / type ntfs (binary,auto)
> B: on /cygdrive/b type ntfs (binary,posix=3D0,user,noumount,auto)
> C: on /cygdrive/c type ntfs (binary,posix=3D0,user,noumount,auto)
> D: on /cygdrive/d type ntfs (binary,posix=3D0,user,noumount,auto)
> E: on /cygdrive/e type vfat (binary,posix=3D0,user,noumount,auto)
> F: on /cygdrive/f type ntfs (binary,posix=3D0,user,noumount,auto)
> H: on /cygdrive/h type nwfs (binary,posix=3D0,user,noumount,auto)
> S: on /cygdrive/s type smbfs (binary,posix=3D0,user,noumount,auto)
>
> ls -al b:/
^^^
This is not POSIX path syntax. Any unexpected behavior from using this path
syntax isn't considered a bug.
> ls: cannot access b:/..: No such file or directory total 0
> drwxr-xr-x 1 user1 None 0 Dec 5 2012 .
> d????????? ? ? ? ? ? ..
> drwxr-xr-x 1 user1 None 0 Dec 5 2012 admin drwxr-xr-x 1 user1 None 0 Nov 18 17:50 global
> drwxr-xr-x 1 user1 None 0 Dec 5 2012 man drwxr-xr-x 1 user1 None 0 Dec 5 2012 WTI
>
> ls -al /cygdrive/b
> total 0
> drwxrwxrwx 1 ???????? ???????? 0 Dec 5 2012 .
> dr-xr-xr-x 1 user1 None 0 Nov 18 18:06 ..
> drwxr-x--- 1 ???????? ???????? 0 Dec 5 2012 admin
> drwxrwxrwx 1 ???????? ???????? 0 Nov 18 17:50 global
> drwxr-x--- 1 ???????? ???????? 0 Dec 5 2012 man
> drwxr-x--- 1 ???????? ???????? 0 Dec 5 2012 WTI
And now you see the expected results.
> What is really strange is that the access via b:/ yields different
> access rights than /cygdrive/b
Explained above.
> I would be really helpful to find a way to use this drive as
> /cygdrive/b/ with the same access rights as for b:/
Supporting DOS-style paths is not a goal of the Cygwin project. Where they
work as expected, we happily let them be used. Where they do not, we
recommend using the supported POSIX paths.
--
Larry
_____________________________________________________________________
A: Yes.
> 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
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
More information about the Cygwin
mailing list