delorie.com/archives/browse.cgi | search |
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:to:subject:message-id:reply-to | |
:references:mime-version:content-type:in-reply-to; q=dns; s= | |
default; b=uBep3hRE962t+WXEVzhxPQKLd2wESKrcydbCzOJqX+w6XWEvjopxS | |
6nnvOjox+b8ZJ0o7zYPEJtxQVtvj1aBrUjQPkUdltX7oEJ1LOD+z8mQ/RpV5VrBm | |
seCU35xUTLJo4gGSWnN/CLltEi3H5qpvY9mBlGKSKnBm/oO24kzaw4= | |
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:to:subject:message-id:reply-to | |
:references:mime-version:content-type:in-reply-to; s=default; | |
bh=1vwAPXw7MlX2OqO2dNarOO1Rpz8=; b=X3WORwSORNAl43WYUpIo8eBAh2SV | |
fFKGZoPbBozXjZFti4XhjBp+QxJB0rWGJM67xCIuftMdViLRdPdnKy9WSvpp0gxi | |
Far088z8QkpFRhNxOWlq2A+HXi1Qw4t+fU0JtXh+iz7udNhs8vZHC2DTqOJ3zGfO | |
CWjAzGEU/VwnGrY= | |
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=-5.9 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.2 |
X-HELO: | calimero.vinschen.de |
Date: | Fri, 5 Dec 2014 11:13:02 +0100 |
From: | Corinna Vinschen <corinna-cygwin AT cygwin DOT com> |
To: | cygwin AT cygwin DOT com |
Subject: | Re: Cygwin AD integration home/shell changes |
Message-ID: | <20141205101302.GI3810@calimero.vinschen.de> |
Reply-To: | cygwin AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
References: | <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> <118770258 DOT 20141203164448 AT yandex DOT ru> <20141204094054 DOT GC3810 AT calimero DOT vinschen DOT de> <1682125876 DOT 20141205080743 AT yandex DOT ru> |
MIME-Version: | 1.0 |
In-Reply-To: | <1682125876.20141205080743@yandex.ru> |
User-Agent: | Mutt/1.5.23 (2014-03-12) |
--jhQDtFD6/0rlgiNE Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Dec 5 08:07, Andrey Repin wrote: > Greetings, Corinna Vinschen! >=20 > >> >> > Here's what you get: > >> >>=20 > >> >> I finally realized, what was tingling me all this time. > >> >> The implicit fallback mechanics. I'd rather want to have explicit d= eclaration > >> >> and a failure message in case something isn't right. Much easier to= fix system > >> >> issues, when the system tell you about them. > >>=20 > >> > 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 maint= ain > >> > your solution, e.g. > >>=20 > >> > db_home: cygwin /invalid/read-only-path > >>=20 > >> Why not set defaults (in case of db_home) to > >>=20 > >> db_home: cygwin desc /home/%U > >>=20 > >> and remove fallback? > >> It just not seems right - creating workarounds to implement straight b= ehavior. >=20 > > 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. >=20 > If you mean "complain and set home to the root", then I'm happy with this > solution. No complain. You still seem to have a problem to understand that this is underlying functionality under a couple of system calls generating passwd entries for arbitrary accounts. It's *not* necessarily the current account. A user visible complaint for every unconfigured account enumerated via getpwent is quite over the top. Corinna --=20 Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat --jhQDtFD6/0rlgiNE Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJUgYUtAAoJEPU2Bp2uRE+glKwP/0aFNUgMC5dGj3+Ci5lnZVGV MZQ2ZqFaTT2kG40wsh3uAHS97yThv+BkyqyNPvRRxPh1/Wch7CqQtvVQDCK/MmPw Eyc5PpYRtURLfi/eahnRLK+3jDHbUxmgORX5itaCjZXQzvDOLsSlveTjLovkcE8O ANIN0l6nUsDilutxfU/F0+Pr8ATAhYJM6Ym3Wi3pryBO57RSvTBi1GzEWEH4H/zN ohoXMacdKj/fdVg9BXAL/gOfJdezDqtXnG20AWCcpSYTRyzjlR6ooob5f24ol6Cn d+ocB74Q2giSe2iNNXYHdCZDxv+K0lQUC/y9WA44WCWTrNYGPb/EyXwaliUnZ1ON dAmZzxZJUcy6zBx01PAFW5ORjHhQZHSymX/0EMxIQkvDb/H/M39rNub5z9ALXKVN gGNxXgPRd+OkFgvVhhMVMbEZq9dgY91X4RgxHcmmLg+q28O8oMCGmcz1jS/RLlNY 80K6C3w7aRuC1twD0FOT+Yf4Ce6JqfD3JsuZIHiWEv6dus4JYxLQZKX5pXpDbltg 3pILyDlPa+G7K6X/JvTVf+Y/Js3SFxKvE3wggvyOgc7RH7FMD2Rgxjd5OX8CEgUP 6ynUDmOIQ9toexW07Yrb52tNAAerOMWCkg8WTyMjrTA/9HXDG0cCSnPHVnthAS/X SQoasr7KAU9lEZpy0Sji =LoRe -----END PGP SIGNATURE----- --jhQDtFD6/0rlgiNE--
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |