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=N8RfXuw6wbkZR3GEJIfkMS9hdIm2cR3gatvr9hPUlpY3fE9YZV2zb CaFMLfaen3lXs5OHVgSW6GJ9mKQIP3OvQcCQ/FPtQ1eV99pjHHS1dE54BqsmegGP bmngli6vw6TEC+U5K6xAX1MLJiVmzLtPN59kqD04BH3eEANWQvD1ag= 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=75qvgFS7M+jM3l+tj9PrsVBUFhs=; b=FEqaUY8U8hEMDKmNmkShTRbSSHlP gTxYASJJcVACM/5yJjrhraejuUQo4EdAKAVbBx2X4BX6PBGqYP4ZxnqvHnrAGVsz Wpp6182bSNZqDl7KJm7EkC7jrMSUBtN7U+6MaQegmwKClrm9cqzm3DVtZSX6GMaa SpnfE9hoTl7jBik= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , 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 Subject: Re: dos telnet.exe not showing up with cygwin "ls" Date: Fri, 18 Apr 2014 20:06:39 +0000 (UTC) Lines: 34 Message-ID: References: <20140418041455 DOT GA2382 AT ednor DOT casa DOT cgf DOT cx> 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 Christopher Faylor cygwin.com> writes: >On Fri, Apr 18, 2014 at 03:35:28AM +0000, Andy wrote: >>I'm using telnet to log in to my modem for certain actions that >>can't be done via its web interface. The thread at >>http://www.cygwin.com/ml/cygwin/2013-08/msg00124.html indicates that >>telnet is normally in Inetutils, and if I don't see Inetutils when >>running the cygwin Setup.exe, > > You aren't looking hard enough. It's "inetutils" and it is > included. > > You can see it here: http://cygwin.com/packages/ Boy, I feel like an idiot. Thanks, Chris, for that reality check. You can't imagine what I was thinking. (I can't believe it either). I equated packages to the categories in the cygwin Setup GUI. And I did do a search for telnet in the cygwn packages search, but of course, millions of hits came up. Then, when I ran into the thread about inetutils, it didn't occur to me to go back to search for it. I actually muscled through the problem using the Windows telnet and manual copy and paste from the DOS window. So the problem was no longer current when I originally posted. However, I described the (solved) problem to head off questions of why I was poking around with the Windows telnet.exe. 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. -- 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