public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Larry Hall (Cygwin)" <reply-to-list-only-lh@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: can not mount Windows shares correctly
Date: Mon, 18 Nov 2013 18:36:00 -0000	[thread overview]
Message-ID: <528A5E19.8020305@cygwin.com> (raw)
In-Reply-To: <8CCC8F85C5F2784387A32FAD835FB4E60C2B6951F1@server03.company.internal>

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

      reply	other threads:[~2013-11-18 18:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-18 18:11 DEWI - N. Zacharias
2013-11-18 18:36 ` Larry Hall (Cygwin) [this message]

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=528A5E19.8020305@cygwin.com \
    --to=reply-to-list-only-lh@cygwin.com \
    --cc=cygwin@cygwin.com \
    /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).