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=iFXadrganzbHQDoIRS14I4Gju2nGKmyZzlJxFTYpBzqNiZdnEOB/G
	DBTE/aCQREtDcpf5RZOSbK6myHPLzMKhLglXT6xtcXOEIWyLyMUOjkyfPcl6FizV
	AFua548LTVenBNZimfNuhdmz1D1FoP1RhqKRkQ5SqiDZlmpcLPMnvc=
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=rugXB6gDcQ7IFfto+Otyw5Hid/8=; b=ev7o/sjiEmSRL6QpprrrQalsLm9g
	zQ2f6TNsao26xjdSl9eXQo21wm2oLJPDrcQwSqj9g3lfVfNpPeQDMyStnhsobD1p
	Y9xzpg8ouMAxlZqKWAM1nmnFfmIlhSLjuVUirMWsQSdLF845T97Ur2bnuI7PQ/9i
	eHLXsimSz6KBXHo=
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:	Thu, 4 Dec 2014 14:46:56 +0100
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: RFC: 1.7.33 problem with user's home directory
Message-ID:	<20141204134656.GG3810@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<8610043342 DOT 20141128150810 AT yandex DOT ru> <20141128124814 DOT GM3810 AT calimero DOT vinschen DOT de> <5354135 DOT 20141128190818 AT yandex DOT ru> <20141128163305 DOT GN3810 AT calimero DOT vinschen DOT de> <1601998502 DOT 20141129012136 AT yandex DOT ru> <CABa6CEkyyae6GGxVSZ6MBP=-d_uq+Uu9qTZEtZfdVHa7KwOs=g AT mail DOT gmail DOT com> <5710377370 DOT 20141202082928 AT yandex DOT ru> <CABa6CEnWihyzxbwydndnLhg9aAfok0iQE7MX+FaMaJ4ewmxCPQ AT mail DOT gmail DOT com> <352663012 DOT 20141203231050 AT yandex DOT ru> <548051A3 DOT 9030203 AT tlinx DOT org>
MIME-Version:	1.0
In-Reply-To:	<548051A3.9030203@tlinx.org>
User-Agent:	Mutt/1.5.23 (2014-03-12)

--7AAf1pfr5RnNeEo0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Dec  4 04:20, Linda Walsh wrote:
> Andrey Repin wrote:
> >Greetings, cyg Simple!
> >>>>Don't forget that CMD will not create a second connection to a
> >>>>\\host\share if Cygwin already has one open.
> >>>What do you mean by that?
> >
> >>$ cd //somehost/someshare
> >>$ cmd /c start cmd
> >
> >>cmd will complain about UNC paths and start in %WINDIR% instead.
> ----
> Try it the other way around.  You'll get the same result.
>=20
> It has nothing to do with cygwin opening it first.  It has
> to do with cmd not handling a "\\network\share" style address.
>=20
> MS was too lazy to deal with command.com's "1-CurDir / drive"
> scenario that is embedded in the Win32 interface.  If you cd to
> //host/<currentdir>, //host isn't a drive letter.

It will get interesting with the new CMD from Windows 10.  MSFT has a
whole team now working on pulling CMD into the 21st century of CLIs.
Allowing UNC paths as CWD is apparently on their radar, though the
current latest CMD in the W10 preview is still missing this feature.

> So what happens when the user uses an absolute path?  "/tmp"...
> where is that /tmp?   Ends up at the root of each drive, but on
> a UNC-based-net-connection?  Undefined.  So cmd.exe can't be used
> on a UNC-based path, only on DOS compatible (drive letter
> assummed) based-path.

Allowing CMD as shell wouldn't change how Cygwin tools see the world.
Yes, with current CMDs you won't be able to utilize network paths as
CWD, among other restrictions.  Still, evaluating "db_shell: windows" as
using CMD, rather than being a no-op might hvae some value.  I would
never use it myself, but there may be some people, or, let's assume,
special maintainance accounts, for which this might come in handy.

Would it hurt to implement it, even only for symmetry with the other
options?  I'm not sure.


Corinna

--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--7AAf1pfr5RnNeEo0
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJUgGXPAAoJEPU2Bp2uRE+g9UwP/i9WTceULBWCyX5Parv5KP4I
1KejokJ17Z9SCYpccBkqGDrXmxrPzudh1ky31l0frZD8SQGdIIoFL6/hUHrvbbY6
A/Znb3Ik1c5waO0wyYFsCfOW69cCusHzICC4XjSiB0oFZEw+lX9RSndhaLs5MBC3
dKof1Kcu3d28T8i8UyVh71wYEx3VAbZlPTpT26sXQBfV2McmKI5vcJdQ2O3rWC9A
KwJ6RQBRACdtyQkhqLyEFMdGk2qpb7+5Spvwx8WNpjZNmobhvW4VV+x36xJPeF30
E43QGtL0evXb4PP9mGbW6c4NalZK/bLoz+mhUiI+eSbbXYTyB3bB0G1L1Aha17qw
dzA8LDEda9pcT26/jT6zANSxNwTtDqG4h8aSSz3WQk4RdfogqRm3TBq/McElI8o0
elzNNu0IYoOI2g+ejmOKq8OBvX8c/UAFJnIkpFg/S8dDb0pk7u0hygAuUeP+D5c8
gJJnVEKINA+2TRV86KuAHmPoBmScmyp78gOxASoE7cU/a1c0JD/62y/ydHzFP/Ds
shScpJJxuU8YJipnWt1k/WN3X/TtGbTlE5z/0EsbBQmwUIpVuO1fu4DoP+V5M8k8
miEduLbMpwQTwtue87TBMzn0Sj6q64SUycXKK1U7CsryrX3kTKwcUexbU7s7RkAA
bJ8e66ofHauWXZdwWjBd
=qxJ6
-----END PGP SIGNATURE-----

--7AAf1pfr5RnNeEo0--

- Raw text -