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 From: Dominique de Waleffe MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Message-ID: <16067.34423.565000.192717@missioncriticalit.com> Date: Thu, 15 May 2003 14:22:15 +0200 To: lhall AT rfk DOT com Cc: Jorgo Miridis , cygwin AT cygwin DOT com Subject: Re: 1.3.22-1 cannot find certain commands In-Reply-To: <3EC292E9.2070905@rfk.com> References: <3EC292E9 DOT 2070905 AT rfk DOT com> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id h4FCP2123861 >>> "Larry" == Larry Hall (RFK Partners, Inc ) writes: Larry> Jorgo Miridis wrote: >> I used the latest installer 2.340.2.5 and installed cygwin. >> >> When executing 'ls' in bash I get: ‘bash: ls: command not found’ >> Also 'df' doesn’t work. >> >> I tried other commands: find, type, grep, etc. They DO work. >> >> I searched for the excutables ‘ls’ and ‘ls.exe’ but they do not exist in >> the cygwin tree. >> >> Is ls a shell builtin? Larry> No. You can find what package it (and any other utility) is in at Larry> . >> Can anybody help me find out what's wrong? Larry> If the above doesn't provide the pointer you need to solve Larry> your problem, please visit Larry> for information on providing this list with a problem report. Larry> This report will help someone here can understand your Larry> installation. I have experienced that type of problem too: I could not execute find, even though it was in the path. After my recent upgrade, I had troubles to execute 'lib' but lib.exe was working: I tracked it to the existence of a directory named lib in one of the path's. My offfice mate also has problems calling certain programs, e.g. head even though it is present in that the path. The problem is a bit different but has the same level of annoyance: in the case of head. The 'head' of perl is called even though perl is later in the path. Calling head.exe works. Is anyone trying to address this type of issues. D. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/