X-Recipient: archive-cygwin@delorie.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=iJ2MTUvuocdHDQim
	41zitogik8PGk3rlTUrAc2r3y89H7XaZxAm2rs+chcj1/LU0BOjtjXF2bNVV9k2o
	yS69UhJN1sFuBWrdW61JWFmjvzlrpzQzupBjMXCMrWYw5s8MMz5PEi9GhWYiwK3m
	+r2p9UOmcnpwrM/PjODIIifPUKA=
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=G3sP0HBkk7Tks/moSGsE/J
	wfCYk=; b=kvjP3CldTxxIZrQWp/DFyE7cyl9cSK7rHFO6OT2ZVO78b7rNvuac7Q
	UtpiuvUCCVIJlJzo9yOS/EHpJR2yi9luFagXP6saaMvdT0BAnQOwLGfjbMiDDSo3
	M/cm8k4sPIH7yNHt3hLaIMBUW5BHtGA33EpIPQ/aDnhtFM4PzTdH4=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=3.0 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,KAM_BODY_URIBL_PCCC,KAM_FROM_URIBL_PCCC,KAM_THEBAT,RCVD_IN_PSBL,SPF_SOFTFAIL autolearn=no version=3.3.2
X-HELO: smtp.ht-systems.ru
Date: Wed, 21 Jan 2015 02:45:50 +0300
From: Andrey Repin <anrdaemon@yandex.ru>
Reply-To: cygwin@cygwin.com
Message-ID: <1408516413.20150121024550@yandex.ru>
To: Corinna Vinschen <cygwin@cygwin.com>, cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 1.7.34-003 (Christmas/New Year release)
In-Reply-To: <20150113090938.GR15791@calimero.vinschen.de>
References: <announce.20141217131626.GR10824@calimero.vinschen.de>   <87oaqynpzq.fsf@Gertrud.fritz.box> <20150107174122.GB4190@calimero.vinschen.de>  <20150108171825.GB15791@calimero.vinschen.de> <8761cez7qi.fsf@Rainer.invalid>  <20150112103834.GA15213@calimero.vinschen.de>  <1317243972.20150112155044@yandex.ru>  <20150112142131.GK15791@calimero.vinschen.de>  <462951490.20150113065357@yandex.ru>  <20150113090938.GR15791@calimero.vinschen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

Greetings, Corinna Vinschen!

>> >> >> > I added a %H specifier to the /path schema which is substituted by the
>> >> >> > Windows home path in POSIX notation.  So, what you should be able to do
>> >> >> > now is something like:
>> >> >> >
>> >> >> >   db_home: /%H/cygwin
>> >> >> 
>> >> >> I've used
>> >> >> 
>> >> >>    db_home: %H/cygwin
>> >> 
>> >> > Meep!  Did you read the preliminary user's guide?  You really should.
>> >> 
>> >> >   https://cygwin.com/preliminary-ug/ntsec.html#ntsec-mapping-nsswitch-passwd
>> >> 
>> >> > The leading slash is in integral part of the "path" scheme,  The above
>> >> > is not recognized as valid entry at all.
>> >> 
>> >> Speaking of validity of entries.
>> >> I was toying around with my chain of VM's, and got to think about a way to
>> >> debug new nsswitch.conf configurations.
>> >> Is there an easy way to see, what steps are performed, and what results are
>> >> returned, from schemes specified in nsswitch.conf ?
>> 
>> > I'm not sure I understand the question.  Just change the db_home
>> > or whatever entry to another one and start another mintty?
>> 
>> That would be an indirect test, that doesn't tell a whole lot if things not
>> work to the expected results.
>> I'm trying different configurations right now, but it seems the result always
>> /home/$USER. And I'm not sure, if it is my misunderstanding, mistakes in my
>> cygwin configuration, or errors in system configuration?
>> It would be wonderful to have a way to directly test different schemes, even
>> if only for current user.

> I don't see the difference.  If you don't get the desired results,
> explain the setting you test and what you did.  Let's discuss it.  If
> it's a bug, I'll fix the bug.  If it's a misunderstanding on your part,
> let's try to improve the documentation.

Sorry for the holdup, I was trying to crack it by myself.
But I was unsuccessful, and have to reach for help.
Even the most striped down configuration doesn't produce visible improvements.

The setup: A Win7 machine - member of a NT4-style domain. (No AD yet.)
Logged in as domain user with admin rights.
Current profile path is C:\Users\<username>.<domainname>
group/passwd files are moved away.

Contents of nsswitch.conf (the last, stripped down next to nothing attempt):

passwd: db
group: db

db_home: /%H
db_shell: /bin/sh


> set HOME
HOMEDRIVE=C:
HOMEPATH=\Users\anrdaemon.CCENTER

> getent passwd %USERNAME%
anrdaemon:*:1051576:1049089:U-CCENTER\anrdaemon,S-1-5-21-1031481445-3291699540-3997755762-3000:/home/anrdaemon:/bin/bash


If I understand it right, the /%H should always return usable value, so do
/bin/sh. But I can't get it to work.
The only other change I can think about is shortened /cygdrive prefix

none / cygdrive binary,posix=0,noacl 0 0

Reverting it back doesn't make a difference.


--
WBR,
Andrey Repin (anrdaemon@yandex.ru) 21.01.2015, <02:09>

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

