public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Daniel D <ruby_user@hotmail.com>
To: <cygwin@cygwin.com>
Subject: error mounting smb shared with ~ in name
Date: Sat, 31 Mar 2012 04:52:00 -0000	[thread overview]
Message-ID: <BAY156-ds13727AB95EF851A7E89C5E9D4E0@phx.gbl> (raw)

Howdy,

Is ~ allowed on a smb share name when mounting it? I keep getting errors 
while trying to mount //server/~foo via fstab.

If yes, can someone give me some tips for what to do to mount a share named 
\\server\~foo ?

Here’s what I already tried:
    - ls //server/~foo works – prints out the content for the dir
    - editing fstab, and adding
        //server/~foo /mnt/~foo smbfs binary,noacl 0 0
    then doing
        mount –a.
    This printed out
        mount: /mnt/~foo: Invalid argument
    - changing in fstab, from //server/~foo to //server/xyz  -- this worked. 
I.e. mount –a does not print out ‘mount: /mnt/~foo: Invalid argument’, and 
`ls /mnt/~foo` prints out the content of //server/xzy
    - mounting the smb share directly did not worked either. Running
        mount //server/~foo /mnt/foo
    also prints out the invalid argument error.
It looks like mount command does not like ~ in the smb share name, though it 
is fine with ~ in the the mount point name. Unfortunately changing the share 
name is not an easy task, and I prefer making this work rather than always 
using long paths with hard-coded remote hostnames.

TIA for any help. 


--
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:[~2012-03-31  4:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-31  4:52 Daniel D [this message]
2012-03-31  6:26 ` Thorsten Kampe
2012-04-01 17:00   ` Daniel D
2012-04-02 14:00     ` Thorsten Kampe

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=BAY156-ds13727AB95EF851A7E89C5E9D4E0@phx.gbl \
    --to=ruby_user@hotmail.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).