X-Recipient: archive-cygwin@delorie.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=U1Rp/cbvPrFJz5Lz
	IduGCnuRI9ok5KPqBpbIwRp8pLAa8waOqKNzUOaDc/prN1OE98KPmLjm8htJQGxP
	FHnkChgaA64aiKtma3QYWeQ/XdVT+J3An6VD+KRSAJQ0ccE5vFU2l8/gw/6Uqfpm
	rJJfwNnGf1lFyu89VK9eRXbO2hY=
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=1i0uUGK2bex9SN7DZJFQCg
	HWKIs=; b=GBXEGlhk6jYEf+fGSMvTBphnaYtXGJhKCQujuL60wntbl2Gt9DzQSx
	8KACqnraExlJ7q/EOtQgV4Uzz4ipGwnP37L4IvacxaoN/4zVLrDVwx3RJLSHWqi9
	+UtetezuGs48zKLGlSSv3vUyEl5kI7rl0JbfepSevgXF/24ov0Sns=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-1.4 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2
X-HELO: vms173019pub.verizon.net
Message-id: <535192CE.6020909@cygwin.com>
Date: Fri, 18 Apr 2014 17:02:06 -0400
From: "Larry Hall (Cygwin)" <reply-to-list-only-lh@cygwin.com>
Reply-to: cygwin@cygwin.com
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-version: 1.0
To: cygwin@cygwin.com
Subject: Re: dos telnet.exe not showing up with cygwin "ls"
References: <loom.20140418T052138-113@post.gmane.org> <20140418041455.GA2382@ednor.casa.cgf.cx> <loom.20140418T215656-767@post.gmane.org>
In-reply-to: <loom.20140418T215656-767@post.gmane.org>
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7bit

On 04/18/2014 04:06 PM, Andy wrote:

<snip>

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

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