public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: [bug?] cygwin cannot mount smb shares beginning with underscore; "Invalid argument"
Date: Mon, 23 Jan 2023 14:19:48 +0100	[thread overview]
Message-ID: <Y86JdADL2IRYpY79@calimero.vinschen.de> (raw)
In-Reply-To: <ec859fb8-6d32-49fc-d87a-4246d2ea92fc@Shaw.ca>

On Jan 22 12:56, Brian Inglis via Cygwin wrote:
> On 2023-01-22 12:21, Corinna Vinschen via Cygwin wrote:
> > On Jan 21 11:30, Jeremy Hetzler via Cygwin wrote:
> > > First, thank you for many years of Cygwin.
> > > 
> > > I'm unable to get Cygwin to mount Windows SMB shares where the share
> > > name begins with underscore. mount gives an error "Invalid argument".
> > 
> > Yes, that's actually a bug.  The mount code path in Cygwin checks
> > the path for being a share (i.e. \\server\share\... syntax)
> > 
> > The code, which, incidentally, has only been marginally changed since
> > its inception pre-2000, is expecting that server name as well as share
> > name both start with an alphanumeric ASCII char.
> > 
> > That means, right now you can't mount servers and shares starting with
> > any character other than [0-9a-zA-Z].  D'oh.
> 
> https://learn.microsoft.com/en-us/troubleshoot/windows-server/identity/naming-conventions-for-computer-domain-site-ou
> 
> looks like embedded not initial or final "-" hyphen/minus is also allowed as
> well as an initial "_" underscore like DNS names.

I also checked
https://answers.microsoft.com/en-us/windows/forum/all/which-characters-are-acceptable-for-a-computer/fddb4895-4295-47ab-a2b9-7773b329718c
and pushed another patch to distinguish valid chars for server name and
share name.

The Cygwin test release containing this patch, 3.5.0-0.139.gcad3913ed8b1,
is just being built.


Thanks,
Corinna

      parent reply	other threads:[~2023-01-23 13:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-21 16:30 Jeremy Hetzler
2023-01-22 19:21 ` Corinna Vinschen
2023-01-22 19:56   ` Brian Inglis
2023-01-22 22:01     ` Jeremy Hetzler
2023-01-23 13:19     ` Corinna Vinschen [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=Y86JdADL2IRYpY79@calimero.vinschen.de \
    --to=corinna-cygwin@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).