delorie.com/archives/browse.cgi | search |
Mailing-List: | contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm |
Sender: | cygwin-owner AT sourceware DOT cygnus DOT com |
Delivered-To: | mailing list cygwin AT sourceware DOT cygnus DOT com |
From: | N8TM AT aol DOT com |
Message-ID: | <ae2396cb.24a05ae9@aol.com> |
Date: | Mon, 21 Jun 1999 23:20:09 EDT |
Subject: | Re: question (latest "stable" dll?) + bugs: vim, bash, gcc, cp, |
find, less, z... | |
To: | John DOT Wiersba AT medstat DOT com, cygwin AT sourceware DOT cygnus DOT com |
MIME-Version: | 1.0 |
X-Mailer: | AOL 3.0 16-bit for Windows sub 85 |
In a message dated 99-06-21 18:43:31 EDT, John DOT Wiersba AT medstat DOT com writes: > 3) The following two commands cause bash to hang for several seconds before > executing properly. I believe that bash is, for some reason, going out to > the LAN before figuring out what to do. Could it be related to bug #1? > cd / > cd relativepath/subdir cd seems quite sensitive to the installation environment, which I don't see specified. My personal experience: NT4SP3 installed on FAT, on LAN: slow but bearable NT4SP5: somewhat better (?) W2K installed on FAT: totally unworkable W2K installed on NTFS5: excellent W95: generally good -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |