DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=s1ghngZ/kvJvhaifwdcPhtOJ/cBv/AdRcT2kZIB+9l5
	FgCcZWqWzppzYzZekUq9PgymdI1SeeN3KId3qqzXyGFn4TTtMHY/8shl2+jUovAG
	dG1HM3XjVtsDD4yMYPobhnxYOP3RqDxRzPejQW9DFdvfoHkkW3HUUpURnO74O9bg
	=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <5346E623.5000406@etr-usa.com>
Date: Thu, 10 Apr 2014 12:42:43 -0600
From: Warren Young <warren@etr-usa.com>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: Still testing needed: New passwd/group AD/SAM integration
References: <20140410145323.GB2437@calimero.vinschen.de>
In-Reply-To: <20140410145323.GB2437@calimero.vinschen.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

On 4/10/2014 08:53, Corinna Vinschen wrote:
> * Support for Cygwin user names different from the Windows username.
>
>    This is a really fat problem.

Who needs this functionality?

Is it some legacy of passwd(5) compatibility, such as the wish to have 
colons in Windows login names?

Does the move to AD/SAM eliminate the original need, so that you 
actually have *two* reasons to stop paying the runtime expense?

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