Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sourceware.cygnus.com
Message-ID: <1ca301bf8f75$3504b5f0$247807a3@sps.mot.com>
From: "Chris Nappi" <ra5809@email.sps.mot.com>
To: <cygwin@sourceware.cygnus.com>
Subject: Re: Cygwin performance (was [ANN] PW32 the...) 
Date: Thu, 16 Mar 2000 12:26:54 -0600
MIME-Version: 1.0
Content-Type: text/plain;	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit

I know that I would GREATLY appreciate it if someone would put some sort of stat_lite into ls.  I work with cygwin almost exclusively over a Samba connection, and have been forced to use the ls from the Microsoft Unix toolkit because the speed on ls -l, ls -CF and ls --color is so slow over a network drive.
Chris
Heribert Dahms <heribert_dahms@icon-gmbh.de> wrote:

> are you hardwired to 'ls', 'ls -l'  or (like me) 'll'?
> My stock b20 'ls' spits out only filenames!

>I usually use 'ls -l', but what I really want (usually) is the filenames,
>sizes and mod times (and sometimes permissions). And, if I want that, I'll
>have to take the stat() penalty, I guess. So...I was curious...what is it in
>he stat() call that can only be obtained by opening the file? Is it just the
>ygnus stat() emulation that does that? One of these days, maybe I'll try out
> native-Win32 perl 'ls' wrapper script...

>cott.Blachowicz@seaslug.org


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com