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=aA0R8n4c6Qkhtnr3R4l3nuMGBnEr4h4Hm13Ad7OMJuEH9k+mFhITt
	0X5mDse4r8MMf+NJ3KzlYdj6VFewtJkTlobnudE2+AqtdzrYjeluu92pz247WH6C
	nYk8C/OE4ev/5js43EmvuIHkDHBR8WPWehI/JqUunOuVDKEQvl9rqY=
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=9YJrbdf7u4s2psifynJdIocmfgQ=; b=mhvqr90R4NgOXEHwB2oG6ueXsoUm
	iTr9NoLNyNYXy6P9W8Wu1u0+NpbDI4UaIPVsZ+Ev9VigckMGTFWjDa+kf5D/euYZ
	2rTogMHrf1IXF2lMZ5oN6TMPWw2VSvOWoprTOubpR5ZiHfeyEXc6EqWKf11PxcG3
	CWUj6nKEJvjltDk=
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=-3.7 required=5.0 tests=AWL,BAYES_20,EXECUTABLE_URI,KAM_EXEURI autolearn=no version=3.3.2
X-HELO: calimero.vinschen.de
Date: Sat, 19 Apr 2014 11:42:27 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: dos telnet.exe not showing up with cygwin "ls"
Message-ID: <20140419094227.GF16638@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <loom DOT 20140418T052138-113 AT post DOT gmane DOT org> <20140418041455 DOT GA2382 AT ednor DOT casa DOT cgf DOT cx> <loom DOT 20140418T215656-767 AT post DOT gmane DOT org> <535192CE DOT 6020909 AT cygwin DOT com> <loom DOT 20140419T003229-712 AT post DOT gmane DOT org> <5351BD02 DOT 8060209 AT cygwin DOT com> <loom DOT 20140419T023433-477 AT post DOT gmane DOT org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;	protocol="application/pgp-signature"; boundary="DiL7RhKs8rK9YGuF"
Content-Disposition: inline
In-Reply-To: <loom.20140419T023433-477@post.gmane.org>
User-Agent: Mutt/1.5.21 (2010-09-15)

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

On Apr 19 00:41, Andy wrote:
> Larry Hall (Cygwin <reply-to-list-only-lh <at> cygwin.com> writes:
> >On 04/18/2014 06:36 PM, Andy wrote:
> >> I'm curious about the circumstance that allows a file that is
> >> readable and executable by all to invisible to cygwin.  Just
> >> something to be aware of when using cygwin, that some mechanism may
> >> cause some of the Windows file system to be invisible.
> >
> > Sounds to me like you installed 32-bit Cygwin on a 64-bit Windows
> > O/S.  If so, the issue you're seeing isn't Cygwin-specific.  All
> > Windows 32-bit apps would experience the same thing.  If you need
> > Cygwin to see both 32 and 64-bit apps/dlls on 64-bit Windows, install
> > 64-bit Cygwin.
> >=20
> > <http://cygwin.com/setup-x86_64.exe>
>=20
> Yes, I'm aware of the 64-bit version of cygwin.  I wasn't aware of this
> hiccup between 32 and 64-bit apps (that the former can't see the latter).=
=20
> All the more reason to move to 64-bit sooner rather than later.  When I
> installed the 32-bit cygwin, it was some time ago, when I was concerned
> about compatibility with all things 32-bit.  Now that 64-bit is much more
> prevalent, I the tides have shifted.

As Larry wrote, this has nothing to do with Cygwin:

64 bit apps on 64 bit find their stuff as usual in C:\Windows\System32.

For 32 bit apps on 64 bit Windows, all access to C:\Windows\System32
is redirected to the directory C:\Windows\SysWOW64, which is populated.
with the 32 bit WIndows tools and DLLs.

Since Vista you can also access the 64 bit C:\Windows\System32 from 32
bit apps, by using the fake path C:\Windows\Sysnative


HTH,
Corinna

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

--DiL7RhKs8rK9YGuF
Content-Type: application/pgp-signature

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

iQIcBAEBAgAGBQJTUkUDAAoJEPU2Bp2uRE+gVtoP/2nD42mHYkGgxNwWTiClBdkX
9GJmdjuQdA6wYjOJA60/OjF2Cna9gbPPYIde/42Ml8I5PYJzrcueE3Zrv35J1QlT
WQQoUf1wmh0UxPnuCNhRzbetz4X72JZdnNW1jC0oUHydYobFtVShG6RbtRqmVD0J
ul8o02PvhS+oyp/NU51rUMV3FCSB3AneAqcODZI2pvWGBnrPbnOOfQN8twuPRHEp
DkWq5csEqqX4mdrole5JDT6YoM7u/VkNiY8MTNSdKMK8MklsBu2ebVtwZ3LX70of
rxKlSn7HmtsG+AF/OpCOe7EOIYJSAnD+hTAmy0AkCfulrVuR9iMWx4nLa4yn+61X
opxqS/Tn3u7Y92TYFysyLlJOpmYyEizpv+ED7HYeLYDpHwvvL6Jbt/eXPUgbs3iI
dEYfO72cyFRFxFroaE8ATHg5FeKObZQGohwQhABYoU32sNLYEiHY6wLwE/de2AGw
pAzqu16CxC5RDd2MTfnlmTK2aD0iJbfmxgpFf6sERSCG5OQMHRl4wTFoAHal1hNg
KhygF71tfoLvH85t++R/zRjStiFFHEGYjG06SCmp4uQoqKU42MBA6Rs6/m82ub31
3vycc6f/g3csCYIDl3P33FQojD/8/k0VZAc+xglhVhd91XXaiO8IP5ylkdXBru9q
akF56ldAR9f2M5vyZX1M
=xelC
-----END PGP SIGNATURE-----

--DiL7RhKs8rK9YGuF--