public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Oelke, Dan" <doelke@opticalsolutions.com>
To: 'Timothy Reaves' <treaves@y11a165.neo.rr.com>
Cc: cygwin users <cygwin@sourceware.cygnus.com>
Subject: RE: Time taken for ls -la --color=yes
Date: Wed, 31 Mar 1999 19:45:00 -0000	[thread overview]
Message-ID: <C59D5C0A3D3FD21192BA00A0C9DDB6A80E6F32@bemidji> (raw)
Message-ID: <19990331194500.Vs_8zhCkUft-emyX0Q9ZrIWLFh3AbDQnm2JKotO5aPY@z> (raw)

> >If you add the color or F switches then the CYGWIN1.DLL has to
> >determine the type of file.  It will be opening every regular file
> >listed and reading a line from the file in order to determine the
type
> >of the file.  You can imagine the overhead involved in this.
> 
> No, I guess I can't, as bash under unix does not take this long, and
it would have to do the same thing.

Under Unix with a normal unix filesystem, the filesystem stores
attributes about each file.
With FAT filesystem there are no such attributes stored - cygwin has to
figure them out.
In particular, if a file is executable or not has be to guessed at by
reading 
the first few characters of the file.  So, cygwin has to open each file
to 
determine this which doesn't happen under unix.

Dan


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


             reply	other threads:[~1999-03-31 19:45 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-08  8:41 Oelke, Dan [this message]
1999-03-31 19:45 ` Oelke, Dan
  -- strict thread matches above, loose matches on Subject: below --
1999-03-08  8:34 Timothy Reaves
1999-03-08  9:09 ` Sebastien Carpe
     [not found]   ` < 36E40422.157007C1@atos-group.com >
1999-03-08 10:26     ` Henry J. Cobb
1999-03-31 19:45   ` Sebastien Carpe
1999-03-31 19:45   ` Henry J. Cobb
     [not found] ` <199903081826.NAA16303@acestes-fe0.ultra.net>
1999-03-08 10:38   ` Larry Hall (RFK Partners, Inc)
     [not found]     ` < 3.0.5.32.19990308133351.009bb950@pop.ma.ultranet.com >
1999-03-08 11:29       ` Fergus Henderson
1999-03-31 19:45         ` Fergus Henderson
1999-03-31 19:45     ` Larry Hall (RFK Partners, Inc)
1999-03-31 19:45 ` Timothy Reaves
1999-03-08  6:13 Earnie Boyd
1999-03-31 19:45 ` Earnie Boyd
1999-03-08  5:45 Timothy Reaves
1999-03-31 19:45 ` Timothy Reaves
1999-03-07 18:31 N8TM
1999-03-31 19:45 ` N8TM
1999-03-07 17:39 Timothy Reaves
     [not found] ` < 199903080144.UAA10167@y11a165.neo.rr.com >
1999-03-07 18:45   ` DJ Delorie
1999-03-31 19:45     ` DJ Delorie
1999-03-31 19:45 ` Timothy Reaves

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=C59D5C0A3D3FD21192BA00A0C9DDB6A80E6F32@bemidji \
    --to=doelke@opticalsolutions.com \
    --cc=cygwin@sourceware.cygnus.com \
    --cc=treaves@y11a165.neo.rr.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).