delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2006/04/02/15:37:51

X-Spam-Check-By: sourceware.org
Message-Id: <200604021937.k32JbMHL000678@tigris.pounder.sol.net>
To: cygwin AT cygwin DOT com
From: cygwin AT trodman DOT com (Tom Rodman)
Reply-to: cygwin AT cygwin DOT com
Subject: ls displays nothing - 3/29 snapshot
Date: Sun, 02 Apr 2006 14:37:22 -0500
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

I installed the 3/29 cygwin1.dll snapshot yesterday on a test windows 2000 box. Many
(all?) of our cron jobs ran normally Sunday morning. Today, though, the output
of 'ls' or 'ls -l' from an interactive bash session was always nothing.
I've reverted back to the released cygwin1.dll, and ls is working again.

Sorry for lack of details; not sure at what point the problem started showing up.

--
Tom

--
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/

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019