Chuck wrote:
Folks I could really use some help here. I still cannot get the ls
command to work reliably. It worked for years and about two weeks ago
started sputtering. I have completely unstalled all cygwin packages,
deleted the directories, and reinstalled from scratch. Even just
installing the bare mimimum packages and running a bash shell without X
or even a .profile, ls still fails to output anything 50% of the time.
One other observation I've made is there's a similar program named
"dir.exe" in the /usr/bin directory. It seems to do pretty much the same
thing as ls. In fact the file sizes and timestamps are even the same. It
works every time. I could just alias ls=/usr/bin/dir but that seems more
like a work-around rather than fixing the real problem. Can anyone help
with this? TIA
Can you trim it down to a simple directory with a file or two? If not,
can you determine what is key to making it happen? You may have mentioned
these before but I don't recall and didn't see them in my review of the
thread:
- Do you see this when running locally? From ssh?
- Does it reproduce in bash? In bash run from cmd.exe?
- Is CYGWIN environment variable still unset?
--
Larry Hall http://www.rfk.com
RFK Partners, Inc. (508) 893-9779 - RFK Office
216 Dalton Rd. (508) 893-9889 - FAX
Holliston, MA 01746
_____________________________________________________________________
A: Yes.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?
--
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/
