Magnus Holmgren wrote: > But Cygwin setup doesn't have to open and read thousands of files. > And it's not using cygwin1.dll. The Cygwin layer seems to slow down > things considerably.
Yes, stat is known to be an expensive operation. > I was able to strip down my $PATH a bit (removing KDE for example), > reducing the time needed to generate the list to some minute, but I'm > not quite satisfied with that either. > >> It's too bad so many DLLs are produced in this list. Must they >> have execute >> bits set to be loaded? >> > NT does have separate read and execute bits. I don't know if DLL:s > have to have the execute bits set to be loaded, Yes! >> This is the sort of thing the "-x," "-E" and "-X" options to "mount" >> are >> meant to address. Check them out, they can probably help a lot with >> this >> problem. > > It helps a bit, or even a lot, but at the price that all files will > be tab completed to. Unless I create a mount point to each directory > in $PATH. Do you have that many that this is impractical? Max. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
