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=DEcFevgDM1SnVHe0NPUzBoksGRCcaJDozmmRMKHHyuHaHrnU8mgqF jL17/fbESMggqaDBIJO2b604pVfcGdJANw/TH2VVj85RtCiAjyBY9OcNFru0jV4i m1wpqqGOBZyMd4qFPZAeAXZbEVOUPsZS2lanjQi6pq+F9qk5dGL3PU= 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=VpIOvbAD/cpxoE/X3+n0ZhZsmnk=; b=G07bOk+3AE+fFrYJo4ZJsh2VEeuJ U0bjKoFshdcAGEgNpRBcmGT12FVbiqslX8ajJl0ZtRP6+YFPGdFjuUKkYmgfG9ny coiCwvMrnpd99EaRZtKRr865lJHSgoLZtIdf5b2B/1l0qZ6KFk1Y3s7jOB/PiOwe BqtvxIQxbwD8c8k= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , 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: Thu, 8 Jan 2015 14:34:36 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 1.7.34-003 (Christmas/New Year release) Message-ID: <20150108133436.GO4190@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <87oaqynpzq DOT fsf AT Gertrud DOT fritz DOT box> <20150107174122 DOT GB4190 AT calimero DOT vinschen DOT de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="AFQGHouA0VN8Ovbt" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) --AFQGHouA0VN8Ovbt Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Jan 7 18:41, Achim Gratz wrote: > Corinna Vinschen cygwin.com> writes: > > > but that would produce some rather unwieldy and long paths for certain > > > users. So, instead of specifying the users' home directory directly I > > > would like to mount or auto-mount /home/=E2=89=A4user> to the actual = (network) > > > home directory. > >=20 > > Hmm. That's tricky. There's no automatism for that yet. Nsswitch.conf > > only describes how to create the passwd entry for a user. It does not > > add any mechanism to run at user context switch. And not everybody > > would like to have something like that so it needs configuration. > >=20 > > I'm not opposed to stuff like that if it simplifies admin's job, but on > > one hand we should evaluate first if there's a way to script that, > > rather than to hardcode it into the Cygwin DLL, and on the other hand > > it's not something I'd like to add for the first cut of 1.7.34... >=20 > I agree that this is not something that belongs into nsswitch.conf, but > since those mounts are working a bit differently on Cygwin than Linux I'd > expect that in order to make some auto-mount facility available the DLL > would need to know about it and provide at least some hooks to set them up > correctly before any process tries to use them. Adding a user mount should be scriptable. The actual home directory is the next to last entry in the user's `getent passwd' output. In a profile script, this entry can be used to generate a user bind mount from the actual dir to /home/$USER. Then, set $HOME to /home/$USER. AFAICS this doesn't require any additional DLL support. > > > > - When spawning a process under another user account, merge the use= r's > > > > default Windows environment into the new process' environment. > > >=20 > > > I think this change pulls in additional environment variables with > > > windows path components when starting programs via cygserver/sshd that > > > are not a login shell (and perhaps when the user's login shell isn't > > > bash, so that profile doesn't get run), most notably PATH, TMP and TE= MP. > > > If these variables are used later on by programs expecting a POSIX pa= th > > > there, then things break. > >=20 > > Did you try it? The idea was that these variables are converted to POS= IX > > on the way in... >=20 > They aren't, but even if they were I don't think it's the right thing to = do > for some variables. Slightly edited: Ok, I see. So where exactly is the problem? Variable which already exist in the env are not overwritten ($PATH). Variables which only have a meaning for Windows apps should stay in DOS notation anyway. So what's left? TMP/TEMP/TMPDIR? If that's all, we have two choices, either convert them, or skip them. What's better? Corinna --=20 Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat --AFQGHouA0VN8Ovbt Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJUrodsAAoJEPU2Bp2uRE+gR1oP/jonebZ1q04xMGqv1G+NtwpI HHmuwxEtRmzxtiO2+XIXfXVMGTMdMBxn1VaqTALfyUXmcn+VED7yp2UIp9KJfTR7 o+hbWwb0kQyHfsMvGCQwCDj+zW8NL4akKb2DFQdegG86VBDF6+2OJxq7NAVz+XEg XI6RHI8jjMa4Mh9eoFvVDbfhTh4mHXJMHC+tb3dHERCjKD08I+vpUX2wSZesDn7V n0fACvBJ6+gh3i4OhHMowOLpy6AZcjFH35VepYqB9559zwb0a1Z02nuCuR2Kmavy 6nU8A0hj1KOata0+I9xCat9WjhUIzBtIuKcY7gwVX1fBHneaIMkAAmq0gC4r2a3R bZo7nOJkgEy9GN5kPx7KuQyiwgV/VTijjKOPUMbd9WBU8fyAXFdPKd+9O7KPmX2O JwJsi6I0Gen6zAB/tR1+Sg4VZ7IsfVnuLnFPNc3iYZlgN97t3Weeog4vyueBihRu 418pH5S4pX9rLjDF0+ZE8n6PGdpP0KG+RdNp/EuaM3zwXia9sqWqq6pmoikdebxJ 2VN24Yem08oZS2/YxRv9y0QQ2WbsHSWQ7VoiA00s2Oz2Xe2VMVU4Mr4CBbUQbybB g2sjAezGmyODys6wNpAXhv/SrVGfv49q7I42kBcV1GBJZyWMdzPTxXFw8JTlYavg zmN+9ynQv4l3NugE3sEX =a5g+ -----END PGP SIGNATURE----- --AFQGHouA0VN8Ovbt--