Re: question (latest "stable" dll?) + bugs: vim, bash, gcc, cp, find, less, zip, ls

[John Wiersba <John.Wiersba@medstat.com>]

Since no one has yet suggested a "stable" release of cygwin1.dll after 1/16,
I tried the 5/23 release (it was the earliest one I could find after the
3/28 date mentioned below).  It seems to be relatively stable so far (i.e.
I've used it for several minutes so far!).  I did have to twiddle the
registry settings for mounts (not unexpected, after the comment about mounts
below).

1) It fixed the "find is broken across mounts" and "running a program using
a relative path" problems I mentioned yesterday.  

2) It does not however seem to fix the "cd /; cd relativepath/dir" problem
(apparently going out to the LAN).  Note that cd does eventually work -- it
just hangs for several seconds before figuring things out. 

=> Additional information: it doesn't hang when CDPATH is unset.  It does
hang when CDPATH=.

3) It "semi-fixed" the vim/TERM=linux bug I reported yesterday.  Now, if I
hit backspace several times, vim still locks up, but a cntl-c gets vim's
attention so that the editing session can be resumed.  This is still bad
enough that I consider vim/TERM=linux unusable, but it's an improvement!

-- John Wiersba (john.wiersba@medstat.com)

> -----Original Message-----
> From: itz@lbin.com [ mailto:itz@lbin.com ]
> Sent: Tuesday, June 22, 1999 1:59 PM
> To: pedwards@jaj.com
> Cc: cygwin@sourceware.cygnus.com; John.Wiersba@medstat.com
> Subject: Re: question (latest "stable" dll?) + bugs: vim, 
> bash, gcc, cp,
> find, less, zip, ls
> 
> 
>    Mailing-List: contact cygwin-help@sourceware.cygnus.com; 
> run by ezmlm
>    Precedence: bulk
>    Sender: cygwin-owner@sourceware.cygnus.com
>    Delivered-To: mailing list cygwin@sourceware.cygnus.com
>    Date: Mon, 21 Jun 1999 19:09:05 -0400
>    From: Phil Edwards <pedwards@jaj.com>
> 
> 
>    I'll add/respond to the few that I've encountered.
> 
>    > 4) find is broken across mounts.  find clearly can see the
>    > files/dirs under the mount, but then for some reason, reports "No
>    > such file or directory".  See the bottom of this email for my
>    > cygcheck outout.
>    >    $ find /
>    >       / /a /a/a find: /a/a/new.zip: No such file or directory
>    >       /bin /c find: /c/UNATTEND.TXT: No such file or directory
>    >       find: /c/BOOTSECT.DOS: No such file or directory find:
>    >       /c/WINNT: No such file or directory find: /c/NTDETECT.COM:
>    >       No such file or directory find: /c/ntldr: No such file or
>    >       directory ...  /etc /etc/group /etc/hosts ...
> 
>    I've had the same thing happen to me while trying to run updatedb.
>    Nothing ever got written to the temp file, by the way, so if you
>    were thinking of running locate/updatedb, don't.
> 
> There's a workaround for updatedb: use the --netpaths option.  For
> instance, updatedb --netpaths=//d/.  You'll probably need --netuser as
> well.
> 
> But both these problems are symptoms of a bug in the path translation
> layer that was only addressed on March 28.  A simpler way to
> demonstrate the problem is just to create a mount point and try to
> access a file below it with a relative path.  A real killer bug IMHO
> but MHO doesn't count :-)
> 
> -- 
> Ian Zimmerman
> Lightbinders, Inc.
> 2325 3rd Street #324
> San Francisco, California 94107
> U.S.A.
> 
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com
> 

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