From: lhall AT rfk DOT com (Larry Hall) Subject: Re: bash "pregnant pauses" revisited (B19 on NT 4.0) 16 Aug 1998 12:01:15 -0700 Message-ID: <3.0.5.32.19980814174555.00994480.cygnus.gnu-win32@pop.ma.ultranet.com> References: <19980814232421 DOT A5316 AT riga DOT schoenewald DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: Arndt Schoenewald , Matthias Morche Cc: Cygwin32 Maillist This is a good support for Geoffrey Noer's feeling the // syntax is "off". I haven't looked at the code but my guess is that the paths are not being converted to drive paths but only UNC stype names (//D becomes \\D). CreateFile() and friends will treat this as a UNC for a system called "D" (just as \\. gets converted to the name of the local system) so this is very likely why so much network is involved here. I agree that this seems like a bug... Larry Hall lhall AT rfk DOT com RFK Partners, Inc. (781) 239-1053 8 Grove Street (781) 239-1655 - FAX Wellesley, MA 02482-7797 http://www.rfk.com At 11:24 PM 8/14/98 +0200, Arndt Schoenewald wrote: >Bingo! Mattias was right: after doing a `mount -b D: /D' the delays >are gone. Thank you very much! I am very happy about this solution as >the delays were quite annoying. > >However, I still think this is a bug that ought to be fixed. I remember >reading that single letter //X paths were always taken to mean drive >letters, not machine names. And how comes the system tries to resolve >and access the host name "unknown"? > >If the underlying problem is not easily fixable, it would be good if >these mounts were automatically created during installation. > >Thanks again (also to Larry Hall for his reply), >Arndt > > >On Fri, Aug 14, 1998 at 10:12:12PM +0200, Matthias Morche wrote: >> Arndt Schoenewald wrote: >> ... >> > D:\>echo %PATH% >> > D:\Perl\5.00502\bin\MSWin32-x86-object;D:\Perl\5.00502\bin;D:\WINNT\system32;D:\WINNT >> > >> > And this is from a fresh bash window launched via cygnus.bat: >> > >> > Cygnus Cygwin32 B19 >> > bash-2.01$ echo $PATH >> > /Cygnus/B19/H-i386-cygwin32/bin://D/Perl/5.00502/bin/MSWin32-x86-object://D/Perl/5.00502/bin://D/WINNT/system32://D/WINNT >> > bash-2.01$ >> > >> > But even if I had a stale network drive in PATH, this wouldn't explain >> > why the prompt is often delayed when I just hit on an empty >> > line -- why should the shell search the PATH when there's no command >> > to execute and the prompt is a constant string?! >> ... >> In my case it tried to interpret a Drive named Y as a hostname. Maybe >> You should "mount -b D: /D", after that //D will be automatically >> reduced to /D and can't be misunderstood as a hostname. Give it a try. >> -- >> Matthias Morche (mailto:morche AT sat1 DOT de) >> SAT.1 (http://www.sat1.de) >> >> >>> Linux: the greatest adventure game since the invention of the PC <<< > >-- >Arndt Schoenewald (arndt AT schoenewald DOT de) >IT Technology & Solutions Integrator >Ostenhellweg 31, 44135 Dortmund, Germany >Tel: +49 231 556075 >Fax: +49 231 556049 > > - For help on using this list (especially unsubscribing), send a message to "gnu-win32-request AT cygnus DOT com" with one line of text: "help".