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:to:from:subject:date:message-id:references
	:mime-version:content-type:content-transfer-encoding; q=dns; s=
	default; b=G9nccWvPDuRtnoDBsXkI0P8WzvYctCNLEWLPsmBgqYbg9vy2Jcp2L
	E7vJCuqJ+mXvgvWrOSFLkjOL2VAH1cYQwtIlBUcAs4NUCLRsWqR7sKUgKUkCYeCz
	aT6V4vCaZ5Y9x3QnBUS09dW19KzGiyTeMlPpcvLZRB4VSg+eFzLeho=
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:to:from:subject:date:message-id:references
	:mime-version:content-type:content-transfer-encoding; s=default;
	 bh=xcBYqM3X+gXrCozmbTRhL8XdcMA=; b=pU0XrSB74yCO3ISh4904O2vw4w/l
	s7+Biu5l5WymuQWhIcTxAI3LDS98wi8Xkfhh5DS1FJrrWBtM5sjcuK2/1L5hSqwU
	TxVJdCnptTaKMA9jswUzvRWe60662omCipvtQ39fE+CgWBFjN0PweIS8Sj4a6U82
	PyYgJE6CFKEA4wk=
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=-0.8 required=5.0 tests=AWL,BAYES_00,EXECUTABLE_URI,FREEMAIL_FROM,KAM_EXEURI,RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=no version=3.3.2
X-HELO: plane.gmane.org
To: cygwin AT cygwin DOT com
From: Andy <AndyMHancock AT gmail DOT com>
Subject: Re: dos telnet.exe not showing up with cygwin "ls"
Date: Sat, 19 Apr 2014 00:41:11 +0000 (UTC)
Lines: 23
Message-ID: <loom.20140419T023433-477@post.gmane.org>
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>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
User-Agent: Loom/3.14 (http://gmane.org/)
X-IsSubscribed: yes

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.
> 
> <http://cygwin.com/setup-x86_64.exe>

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). 
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.

Thank you, Larry.


--
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