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 10:26:00 -0000 [thread overview]
Message-ID: <1ca301bf8f75$3504b5f0$247807a3@sps.mot.com> (raw)
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
next reply other threads:[~2000-03-16 10:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-16 10:26 Chris Nappi [this message]
2000-03-16 10:43 ` Larry Hall (RFK Partners, Inc)
-- strict thread matches above, loose matches on Subject: below --
2000-03-15 13:43 Heribert Dahms
2000-03-15 14:01 ` Larry Hall (RFK Partners, Inc)
2000-03-16 9:32 ` Scott Blachowicz
2000-03-16 10:22 ` Chris Faylor
2000-03-13 10:04 [ANN] PW32 the (alternative) Posix-over-Win32 layer 0.3.0 released Earnie Boyd
2000-03-13 11:21 ` Re[2]: " Paul Sokolovsky
2000-03-13 15:16 ` Larry Hall (RFK Partners, Inc)
2000-03-13 15:56 ` Chris Faylor
2000-03-13 16:23 ` Jeff Sturm
2000-03-13 18:08 ` Cygwin performance (was [ANN] PW32 the...) Geoffrey Noer
2000-03-14 16:29 ` Scott Blachowicz
2000-03-14 21:04 ` Chris Faylor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='1ca301bf8f75$3504b5f0$247807a3@sps.mot.com' \
--to=ra5809@email.sps.mot.com \
--cc=cygwin@sourceware.cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).