X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org To: cygwin@cygwin.com From: Mark Geisert Subject: Re: Problem after upgrading from 1.7.9 to 1.7.10-1 - system commands not found Date: Sat, 25 Feb 2012 04:12:05 +0000 (UTC) Lines: 16 Message-ID: References: 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 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Bilig Ordos writes: > After this, I'm still having the same issue - I can only execute the > internal "bash" commands, which are the commands listed by doing > "help" from the shell. I'm not able to run any other commands such as > "ls", "uname", and "man" ... Others have mentioned things for you to try. I'm just going to respond to this little bit above. The commands are likely still present, it's just that until things are fixed you'll have to type a little bit more. You have to give the full path to run commands. For instance, to run 'ls' you have to enter '/bin/ls' and to run 'chown' you have to enter '/bin/chown'. Once the file perms are set properly, as outlined in another response, you won't need to type the extra stuff anymore. HTH, ..mark -- 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