Maybe a "non-cygwin" ls gets in your way. Do the following: (1) Type
bash to ensure that you are running in a bash shell (2) Verify that the ls problem still exists, and if it does (3) Type type -a ls to see which "ls" is being used. Ronald -- Ronald Fischer <rona...@eml.cc> + If a packet hits a pocket on a socket on a port, + and the bus is interrupted and the interrupt's not caught, + then the socket packet pocket has an error to report. + (cited after Peter van der Linden) -- 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
