Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Message-ID: <000d01c28e9a$764b0150$78d96f83@pomello> From: "Max Bowsher" To: , "Randall R Schulz" References: <1037497099 DOT 24907 DOT ezmlm AT cygwin DOT com> <5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20021117161546 DOT 00fd6b08 AT pop3 DOT cris DOT com> Subject: Re: No such file, but it's right there Date: Mon, 18 Nov 2002 00:35:57 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Randall R Schulz wrote: > Cygwin follows the Windows convention of using file file name suffix > ".exe" for its binary executable files. While Cygwin will locate and > execute files files given only the base name (sans suffix), other > uses ("cat," "less," or more apropos "nm," "size" or "file") demand > the full file name, including the ".exe" suffix. Actually, the significant point seems to be that the files are being accessed via a mount with no underlying directory. Max. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/