X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:reply-to:subject:to:references:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=CqlG4A5dpjsaqoXL
	FJ3fTWy0VPNVVMgbhV2+Wb13i6UQj3l3gvfa627vc7EfYsmm6Uh7A30AWTNekkL8
	EO7owx2AZTFpMVc3Fa7a0IdXYuJmWwJQukiSekkwtPY8A3WhNbDQnOW5VHVWBxL+
	BCsR/4neD/LyDuLlR3B5NRIcSdw=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:reply-to:subject:to:references:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=3cM5WkKKnh+GBCDNHMKQaU
	1qMCY=; b=lmTw8MpkhEMGKPWFoyHP6E1CISd+4yC3DcgoSmS9uQUdaw5zpXxzQb
	1wFJzfORkawau/9EARxg1xWT1fht+v2bayGV1dCZCgmsbZl9Y1m7h+eysPDYUzo6
	/v2XVR6OP+Lgy+tkJJmQe/cI/FvQzLq1I2bFH5gW4Te0R4v1Z2BEs=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-1.6 required=5.0 tests=BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 spammy=H*Ad:D*ca, discretion, H*R:D*ca, reader
X-HELO: smtp-out-no.shaw.ca
Reply-To: Brian DOT Inglis AT SystematicSw DOT ab DOT ca
Subject: Re: Windows to Cygwin username mapping: Domain before local account when duplicate name?
To: cygwin AT cygwin DOT com
References: <20190215163817 DOT GI2702 AT calimero DOT vinschen DOT de> <CANV9t=Rm+su=qDqdFN-LqiMLEAHJD7WxW_OSqqSpqgeb6ir++w AT mail DOT gmail DOT com> <20190215202936 DOT GL2702 AT calimero DOT vinschen DOT de> <CANV9t=SdQPZw_VF95HwDrVRU1KzdHA61GJBRgA1weHryHUO6-w AT mail DOT gmail DOT com> <20190215204326 DOT GO2702 AT calimero DOT vinschen DOT de> <CANV9t=Q5M+V9TPEN-GaGzLtK_8AO5fUenajQ+T-VZX6+kbrMMw AT mail DOT gmail DOT com> <3bace8f4-1097-9245-10e9-1ed54d1014f3 AT SystematicSw DOT ab DOT ca> <CANV9t=QDy6Y5X867vrq47jgxTUJU9h95kmmbeCWtotZroEcGaQ AT mail DOT gmail DOT com> <20190216094528 DOT GT2702 AT calimero DOT vinschen DOT de> <959f0e79-1ede-878a-6306-d0bdd8d7ef0e AT SystematicSw DOT ab DOT ca> <20190216153320 DOT GC4256 AT calimero DOT vinschen DOT de>
From: Brian Inglis <Brian DOT Inglis AT SystematicSw DOT ab DOT ca>
Openpgp: preference=signencrypt
Message-ID: <0d77615d-68fb-b1f4-114b-a91379371dc0@SystematicSw.ab.ca>
Date: Sat, 16 Feb 2019 09:15:30 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.0
MIME-Version: 1.0
In-Reply-To: <20190216153320.GC4256@calimero.vinschen.de>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

On 2019-02-16 08:33, Corinna Vinschen wrote:
> 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 Inglis wrote:
>>>>> 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.

As with .\$USER in Windows or with ~ for $HOME, this should only be a
convenience to allow input or scripts to avoid providing $COMPUTERNAME/$HOSTNAME
in userid command line argument contexts.
Should whether $COMPUTERNAME/$HOSTNAME be output as . in userid contexts be left
to each app?

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.

--
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