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:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=BzyYfU8/NYdUpWhx
	R9GoPZC5YNkdfMLZHuKkwVI/lu6uuC1oIvP5UD+/gWTCFjH7vxDsxC1PSPj7Qt+x
	eysGO7d+fM989NRrySCJaxxF+AA5VupceWmvFxJx6SBW2nE0yw0UGLU+dyvPT4J0
	9YRP2kaso/e69xc8byDu3SENEPc=
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:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; s=default; bh=f1bb7Qyzs1HlMiRh7PiTpf
	M/87w=; b=hfbyJCsWFGzzqPs/9x6VTHy+Ol0gVV8GyKNJPOV8tQ/wf6Xoe80YqL
	Npr1Gq58i5QXQLxn8hM5M1EbJTByOmoO1ROX40uCUAP2ijYTMA4ngFbA35n4p1F2
	WxiPNX+czs/J2Y6lO3ArHJ0GeobFUxsnnZva+VgHJjvd+Ra7LjKAY=
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-Virus-Found: No
X-Spam-SWARE-Status: No, score=1.7 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,KAM_BODY_URIBL_PCCC,KAM_FROM_URIBL_PCCC,KAM_THEBAT,SPF_SOFTFAIL autolearn=no version=3.3.2
X-HELO: smtp.ht-systems.ru
Date: Wed, 3 Dec 2014 16:44:48 +0300
From: Andrey Repin <anrdaemon AT yandex DOT ru>
Reply-To: cygwin AT cygwin DOT com
Message-ID: <118770258.20141203164448@yandex.ru>
To: Corinna Vinschen <cygwin AT cygwin DOT com>, cygwin AT cygwin DOT com
Subject: Re: Cygwin AD integration home/shell changes
In-Reply-To: <20141203091608.GA26844@calimero.vinschen.de>
References: <20141110205216 DOT GJ2782 AT calimero DOT vinschen DOT de>   <0B8D23F7-0258-472D-BF38-860402FD3CDC AT etr-usa DOT com>  <20141111101821 DOT GO2782 AT calimero DOT vinschen DOT de>  <loom DOT 20141111T112847-576 AT post DOT gmane DOT org>  <20141111111437 DOT GB28012 AT calimero DOT vinschen DOT de>  <20141126205658 DOT GA9157 AT calimero DOT vinschen DOT de>  <946685207 DOT 20141203102637 AT yandex DOT ru>  <20141203091608 DOT GA26844 AT calimero DOT vinschen DOT de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

Greetings, Corinna Vinschen!

>> > Here's what you get:
>> 
>> I finally realized, what was tingling me all this time.
>> The implicit fallback mechanics. I'd rather want to have explicit declaration
>> and a failure message in case something isn't right. Much easier to fix system
>> issues, when the system tell you about them.

> The fallback mechanism is pretty much required to have a sane default
> which works for home users without having to change nsswitch.conf at
> all.  Also, not everybody will want error messages rather than some sane
> fallback (for any given value of "sane"), while if you don't want a sane
> fallback, you can easily create an unsane fallback to help you maintain
> your solution, e.g.

>   db_home: cygwin /invalid/read-only-path

Why not set defaults (in case of db_home) to

db_home: cygwin desc /home/%U

and remove fallback?
It just not seems right - creating workarounds to implement straight behavior.


--
WBR,
Andrey Repin (anrdaemon AT yandex DOT ru) 03.12.2014, <16:39>

Sorry for my terrible english...


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