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 being able to run shell >>> scripts any more, either. >>> >>> The other two of us that upgraded last week to the latest Windows cygwin do >>> NOT have this "ls" problem. "ls" works fine. >> I thought it might be a problem with cygwin too so I rolled back the >> cygwin kernel to version 1.5.23-1, and coreutils to 6.4-1. That didn't help. >> >> I'm glad someone else is reporting this. Maybe there's a real problem here. >> >> What hw/os is your colleague working on? Mine is a Dell D610 laptop, >> Windows XP SP2 with all latest patches. > > I doubt that this particular problem is anything other than a missing > package, actually. > > The details listed at http://cygwin.com/problems.html would probably be > helpful. > > cgf >
I don't think it's a missing package. I've been using cygwin succesfully for years and suddenly last week the "ls" command stopped working. I haven't uninstalled or installed anything . All I've done recently is apply the latest kernel package (1.5.24-2). I will repost the problem along with cygcheck output -- 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/
