Shankar Unni wrote:
Chuck wrote:
Any other ideas? Anyone?
Have you followed the problem reporting guidelines at
http://cygwin.com/problems.html ?
Also, if you are familiar with strace, you may want to run strace
/bin/ls in your /cygdrive directory, and see if anything obvious (to
you)
Christopher Faylor wrote:
On Mon, Feb 12, 2007 at 06:04:57PM -0500, Chuck wrote:
Dennis Simpson wrote:
One co-worker downloaded the latest Windows cygwin last week. His ls
command now consistently does not return anything, regardless of what
directory he is in. This is in addition to not
On Tue, Feb 13, 2007 at 09:36:44AM -0500, Chuck wrote:
Christopher Faylor wrote:
On Mon, Feb 12, 2007 at 06:04:57PM -0500, Chuck wrote:
Dennis Simpson wrote:
One co-worker downloaded the latest Windows cygwin last week. His ls
command now consistently does not return anything, regardless of
Christopher Faylor wrote:
You have no basis for jumping on every potential cockpit error and claim
it is YA occurrence of your problem. I don't know what is causing your
problem but the problem reported in this thread is likely to have been
caused by exactly what I said.
Why on earth do
On Tue, Feb 13, 2007 at 11:06:29AM -0500, Chuck wrote:
Christopher Faylor wrote:
You have no basis for jumping on every potential cockpit error and
claim it is YA occurrence of your problem. I don't know what is
causing your problem but the problem reported in this thread is likely
to have been
Christopher Faylor wrote:
On Tue, Feb 13, 2007 at 11:06:29AM -0500, Chuck wrote:
Christopher Faylor wrote:
You have no basis for jumping on every potential cockpit error and
claim it is YA occurrence of your problem. I don't know what is
causing your problem but the problem reported in this
On Tue, Feb 13, 2007 at 12:37:43PM -0500, Chuck wrote:
Christopher Faylor wrote:
On Tue, Feb 13, 2007 at 11:06:29AM -0500, Chuck wrote:
Christopher Faylor wrote:
You have no basis for jumping on every potential cockpit error and
claim it is YA occurrence of your problem. I don't know what is
On Tue, Feb 13, 2007 at 12:47:05PM -0500, Christopher Faylor wrote:
On Tue, Feb 13, 2007 at 12:37:43PM -0500, Chuck wrote:
Christopher Faylor wrote:
On Tue, Feb 13, 2007 at 11:06:29AM -0500, Chuck wrote:
Christopher Faylor wrote:
You have no basis for jumping on every potential cockpit error
Christopher Faylor wrote:
On Mon, Feb 12, 2007 at 06:04:57PM -0500, Chuck wrote:
Dennis Simpson wrote:
One co-worker downloaded the latest Windows cygwin last week. His ls
command now consistently does not return anything, regardless of what
directory he is in. This is in addition to not
On Tue, Feb 13, 2007 at 03:04:40PM -0500, Chuck wrote:
Christopher Faylor wrote:
On Mon, Feb 12, 2007 at 06:04:57PM -0500, Chuck wrote:
Dennis Simpson wrote:
One co-worker downloaded the latest Windows cygwin last week. His ls
command now consistently does not return anything, regardless of
Christopher Faylor wrote:
I have apologized for my previous confusion and imprecise language but
it seems like there might still be lingering confusion on your part as a
result.
There was. Apologies.
I hope that the above clarification serves to put this issue to
rest and that you will
Chuck wrote:
Any other ideas? Anyone?
Have you followed the problem reporting guidelines at
http://cygwin.com/problems.html ?
Also, if you are familiar with strace, you may want to run strace
/bin/ls in your /cygdrive directory, and see if anything obvious (to
you) pops up.
Else, you
On Tue, Feb 13, 2007 at 03:05:35PM -0800, Shankar Unni wrote:
Chuck wrote:
Any other ideas? Anyone?
Have you followed the problem reporting guidelines at
http://cygwin.com/problems.html ?
Also, if you are familiar with strace, you may want to run strace
/bin/ls in your /cygdrive directory, and
Chuck wrote:
$ cd /cygdrive
$ ls
$ ls -a
. .. c g h k s
$ ls -a
$ ls -a
Hmm. Can't replicate this on my system. Nor can I replicate your other
report, about corrupted ls output.
You should definitely report a problem in the format described by
http://cygwin.com/problems.html.
One co-worker downloaded the latest Windows cygwin last week. His ls
command now consistently does not return anything, regardless of what
directory he is in. This is in addition to not being able to run shell
scripts any more, either.
The other two of us that upgraded last week to the
Dennis Simpson wrote:
One co-worker downloaded the latest Windows cygwin last week. His ls
command now consistently does not return anything, regardless of what
directory he is in. This is in addition to not being able to run shell
scripts any more, either.
For the problem with running
Dennis Simpson wrote:
One co-worker downloaded the latest Windows cygwin last week. His ls
command now consistently does not return anything, regardless of what
directory he is in. This is in addition to not being able to run shell
scripts any more, either.
The other two of us that
On Mon, Feb 12, 2007 at 06:04:57PM -0500, Chuck wrote:
Dennis Simpson wrote:
One co-worker downloaded the latest Windows cygwin last week. His ls
command now consistently does not return anything, regardless of what
directory he is in. This is in addition to not being able to run shell
I started noticing a strange problem recently. When I am in the
/cygdrive directory I can't ls anything most of the time. Same thing
sometimes happens in my home directory too but it happens less often.
Here's some sample output. As you can see the /cygdrive
$ uname -a
CYGWIN_NT-5.1
19 matches
Mail list logo
