From: Jeremy Hetzler <jeremyhetzler@gmail.com>
To: cygwin@cygwin.com
Cc: Brian Inglis <Brian.Inglis@shaw.ca>
Subject: Re: [bug?] cygwin cannot mount smb shares beginning with underscore; "Invalid argument"
Date: Sun, 22 Jan 2023 17:01:38 -0500 [thread overview]
Message-ID: <CAOh4nmmyWdbx0c+dtaSz0HOOET8VbSg-E8ftWiXRNDC9FSYqdg@mail.gmail.com> (raw)
In-Reply-To: <ec859fb8-6d32-49fc-d87a-4246d2ea92fc@Shaw.ca>
[-- Attachment #1: Type: text/plain, Size: 1972 bytes --]
Thanks Brian and Corinna.
Jeremy
On Sun, Jan 22, 2023, 14:57 Brian Inglis via Cygwin <cygwin@cygwin.com>
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 pushed a patch and the Cygwin test release 3.5.0-0.138.g6338d2f24a60
> > is building while I'm replying. Should be up in an hour or so.
>
> --
> Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
>
> La perfection est atteinte Perfection is achieved
> non pas lorsqu'il n'y a plus rien à ajouter not when there is no more
> to add
> mais lorsqu'il n'y a plus rien à retirer but when there is no more
> to cut
> -- Antoine de Saint-Exupéry
>
> --
> Problem reports: https://cygwin.com/problems.html
> FAQ: https://cygwin.com/faq/
> Documentation: https://cygwin.com/docs.html
> Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
>
next prev parent reply other threads:[~2023-01-22 22:01 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 [this message]
2023-01-23 13:19 ` Corinna Vinschen
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=CAOh4nmmyWdbx0c+dtaSz0HOOET8VbSg-E8ftWiXRNDC9FSYqdg@mail.gmail.com \
--to=jeremyhetzler@gmail.com \
--cc=Brian.Inglis@shaw.ca \
--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).