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=YeZEgIAyDbanxGWD9VW2bT4XljVvWvifvitqjN1jrvobdcVlW1e9c
	YL4O58aXUzIUhnOdrTldtVA0hhPlamrw0Al5yVBObJfOctppNOe68E1piPUTrGHy
	2euEcDJthvWgZucufJb64WuHuri8N8TcphmrUaeVcgNG9WxH5Xua2s=
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=Zv83/nFinGNOBE9+d2IngeYevQw=; b=nfv2Wh9HvtKYOfoBkxNNOit45PBE
	s2vtv1oyLupC+rWSXRH/0Q85Rvg+5Yz7zZXQaOTccSZI8gSUoBejCQ0bTBP6fCI5
	BouPf+71fJ3ZF6NRsbdVpizNOZbiHYAtOYMR63dTGtEN+Um2OKyAFnavUzNjcHoJ
	K2Ycosmi9Hp8/Lw=
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=-2.0 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham 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:	Fri, 18 Apr 2014 22:36:32 +0000 (UTC)
Lines:	24
Message-ID:	<loom.20140419T003229-712@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>
Mime-Version:	1.0
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 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.


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

- Raw text -