From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Windows to Cygwin username mapping: Domain before local account when duplicate name?
Date: Sat, 16 Feb 2019 15:35:00 -0000 [thread overview]
Message-ID: <20190216153320.GC4256@calimero.vinschen.de> (raw)
In-Reply-To: <959f0e79-1ede-878a-6306-d0bdd8d7ef0e@SystematicSw.ab.ca>
[-- Attachment #1: Type: text/plain, Size: 1186 bytes --]
On Feb 16 08:09, Brian Inglis wrote:
> On 2019-02-16 02:45, Corinna Vinschen wrote:
> > On Feb 15 14:51, Bill Stewart wrote:
> >> On Fri, Feb 15, 2019 at 2:38 PM Brian Ingliswrote:
> >>
> >>> Windows normally allows "." to be used to refer to the local machine name in a
> >>> domain context - can anyone confirm or deny whether this works in Cygwin or with
> >>> getent?
> >>
> >> AFAICT, the "." shortcut does not work in Cygwin.
> >
> > The combining operator for domain prepended usernames is '+'. This
> > is the same character as used by good old Interix for the same purpose.
>
> That was not in question - the question was could .+$USER be used in lieu of
> $COMPUTERNAME+$USER or $HOSTNAME+$USER and should $COMPUTERNAME rather than
> $HOSTNAME be used in such contexts?
Yeah, I misunderstood this, sorry. The answer is no. The username is
fixed. Otherwise you'd have two auto-generated passwd entries for the
same user which may lead to confusion (not necessarily confusion on the
user side...)
If this is a desired feature, we could try this, but it might break
existing setups again.
Corinna
--
Corinna Vinschen
Cygwin Maintainer
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-02-16 15:33 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-14 23:50 Bill Stewart
2019-02-15 10:05 ` Sam Edge (Cygwin)
2019-02-15 15:56 ` Bill Stewart
2019-02-15 16:05 ` Brian Inglis
2019-02-15 16:14 ` Andrey Repin
2019-02-15 16:51 ` Corinna Vinschen
2019-02-15 19:25 ` Bill Stewart
2019-02-15 20:30 ` Corinna Vinschen
2019-02-15 20:43 ` Bill Stewart
2019-02-15 20:50 ` Corinna Vinschen
2019-02-15 21:00 ` Bill Stewart
2019-02-15 21:38 ` Corinna Vinschen
2019-02-15 21:51 ` Bill Stewart
2019-02-16 1:05 ` Bill Stewart
2019-02-16 1:26 ` Andrey Repin
2019-02-19 16:15 ` Bill Stewart
2019-02-19 17:20 ` Bill Stewart
2019-02-19 19:02 ` Andrey Repin
2019-02-15 21:48 ` Brian Inglis
2019-02-15 22:19 ` Bill Stewart
2019-02-16 13:12 ` Corinna Vinschen
2019-02-16 15:33 ` Brian Inglis
2019-02-16 15:35 ` Corinna Vinschen [this message]
2019-02-16 17:14 ` Brian Inglis
2019-02-16 17:43 ` Corinna Vinschen
2019-02-18 9:14 ` Corinna Vinschen
2019-02-15 21:00 ` Andrey Repin
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=20190216153320.GC4256@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).