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=k97YA4CqRuZ5u/BJ
	BHym0uIPpXk5rVsPVFiL9BvuOnOIg3x+5MqIkkbvRr50d3S29/J5K4acpaPORHTZ
	/9HSubQ+e14AnUohu1Q8l4RqzubxisBI5udRuYRj8nfPABRhHhAGoM6D4hbbmpoM
	ywOqqfgPvVLMjizmyWb0fXf8vpY=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Fri, 5 Dec 2014 08:07:43 +0300
From: Andrey Repin <anrdaemon@yandex.ru>
Reply-To: cygwin@cygwin.com
Message-ID: <1682125876.20141205080743@yandex.ru>
To: Corinna Vinschen <cygwin@cygwin.com>, cygwin@cygwin.com
Subject: Re: Cygwin AD integration home/shell changes
In-Reply-To: <20141204094054.GC3810@calimero.vinschen.de>
References: <20141110205216.GJ2782@calimero.vinschen.de>   <0B8D23F7-0258-472D-BF38-860402FD3CDC@etr-usa.com>  <20141111101821.GO2782@calimero.vinschen.de>  <loom.20141111T112847-576@post.gmane.org>  <20141111111437.GB28012@calimero.vinschen.de>  <20141126205658.GA9157@calimero.vinschen.de>  <946685207.20141203102637@yandex.ru>  <20141203091608.GA26844@calimero.vinschen.de>  <118770258.20141203164448@yandex.ru>  <20141204094054.GC3810@calimero.vinschen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

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.

> It's not a workaround from my POV to provide a fallback.  Creating a
> workable passwd entry is important.  If I implement it as you suggest
> above, I would still provide the typical "set home to the root dir"
> default.  Sure, that might be an option.

If you mean "complain and set home to the root", then I'm happy with this
solution.


--
WBR,
Andrey Repin (anrdaemon@yandex.ru) 05.12.2014, <08:06>

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