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:message-id:date:from:reply-to:mime-version:to
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=YwvAlHcky7j9zKSH
	wYhV/tqyki3Zy134BNneswDRXNe32YkTubAO8EQLN2/HKTSmZuLu9i72XQQILoQz
	1StC1bp43lUHVJR/NllZY95PeUX5wZtBrSQwZ040eVFhaMxHYC0GWGTQ1DINFi1A
	pohtXuXgk8hUOqF5PM/av/VvWYU=
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:message-id:date:from:reply-to:mime-version:to
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=WfEsAL6ze67rHRFqF+3wOI
	oXbFA=; b=PHNYIvp08Ydh6hPVQjThxIyvfElSRXrW6KSA62nGOWezGQ5zDzfhzt
	axja/+Qn6fK2SkYoNi5sTcAKw1EjZ4/8W50cyxokfKbqJx5xf36YHQfsxZ6Dl7eJ
	j7JzM06HQOnJtVaSNf5KrIO607B0Bx6yOxBhesjjjX3jYG4ium7h4=
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.1 required=5.0 tests=AWL,BAYES_00,EXECUTABLE_URI,KAM_EXEURI,RCVD_IN_DNSWL_NONE autolearn=no version=3.3.2
X-HELO: vms173021pub.verizon.net
Message-id: <5351BD02.8060209@cygwin.com>
Date: Fri, 18 Apr 2014 20:02:10 -0400
From: "Larry Hall (Cygwin)" <reply-to-list-only-lh AT cygwin DOT com>
Reply-to: cygwin AT cygwin DOT com
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: dos telnet.exe not showing up with cygwin "ls"
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>
In-reply-to: <loom.20140419T003229-712@post.gmane.org>
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7bit

On 04/18/2014 06:36 PM, Andy wrote:
> Larry Hall (Cygwin <reply-to-list-only-lh <at> cygwin.com> writes:
>> On 04/18/2014 04:06 PM, Andy wrote:
>>> The real question (I should have emphasized this in my original
>>> post) is how a file can be invisible to cygwin, but not to Windows
>>> explorer or the DOS shell.  It's a general question that goes
>>> beyond telnet.  The fact that this is possible is (I think)
>>> something to be aware of because it means that what you see using
>>> bash could very well be a low fidelity reflection of what's in the
>>> underlying Windows file system.  I mean low fidelity in a relative
>>> sense -- it means there's one more way for what's seen via bash to
>>> differ from the underlying Windows file system.
>>
>> Can you clarify your question here a bit?  Are you using a 32-bit
>> Cygwin and confused by the fact that you don't see 64-bit stuff with
>> it?  Forgive me if I assumed too much about the issue you're seeing.
>
> It's not really a problem at present, but the file
> c:\Windows\System32\telnet.exe is not visible when I use cygwin's bash to cd
> to that directory and issue the ls command.  I am using 32-bit cygwin.  I'm
> not concerned about having access to functionality, as I have both cygwin's
> and Windows' telnet.  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>

-- 
Larry

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

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