From: "Lincoln, W. Terry" <terryl@ultimatetechnology.com>
To: 'Cygwin Mailing List' <cygwin@sourceware.cygnus.com>
Subject: Re: question (latest "stable" dll?) + bugs: vim, bash, gcc, cp, find, less, zip, ls
Date: Wed, 30 Jun 1999 22:10:00 -0000 [thread overview]
Message-ID: <B3953869CBF8D211A1E50004AC4C1B5402F41A@ultimate2.ultimate.com> (raw)
Message-ID: <19990630221000.D7LEG4Ybwf_P0qaeES5McoM2-yKJETg-rhTYoT1LSXE@z> (raw)
> -----Original Message-----
> From: Chris Faylor [ mailto:cgf@cygnus.com ]
> Sent: Tuesday, June 22, 1999 4:37 PM
> To: WTerryLincoln@engineer.com
>
>
> On Tue, Jun 22, 1999 at 02:55:41PM -0400, Lincoln, W. Terry wrote:
> >> From: itz@lbin.com [ mailto:itz@lbin.com ]
> >> 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 :-)
> >
> >I am afraid I too agree that this is pretty much a utility
> killer of a bug.
> >Perhaps this will someday be addressed and a real solution
> will be put
> >forth. This BUG has crippled many of my out-of-box porting
> attempts. :-(
>
> Did you read the part that said "was... addressed on March
> 28"? What kind
> of "real solution" were you looking for besides a change to
> the DLL which
> fixes the problem?
Sorry Chris,
I have been somewhat reluctant to download and install some of these newer
releases because while a few bugs have been addressed and fixed, I have been
reading about other semi-crippling bugs being introduced.
I have been looking for announcements in this list of significant fixes such
as you mention, but perhaps I lost some mail that did that.
Since I have not been fully apprised of which bugs have been backed out I
haven't bothered to change. Also, since the last DLL I have has been the
most stable _for me_, I didn't install the March 28 version *yet* ;-)
I guess that I will have to update again and hope for increased
functionality (at the expense of changing share
>
> Incidentally, this terrible, unbelievably crippling bug has
> been in cygwin
> pretty much since the beginning.
>
> Also, I could be wrong, but I believe that this is also
> solved by creating
> the appropriate directories in your root, as is suggested
> when you use the
> mount program.
>
> cgf
>
W. Terry Lincoln - Senior Engineer \ \ _ /
Ultimate Technology Corporation \ \ |J| /
a Tridex Company (NASDAQ:trdx) \ _|E|_
ICQ < http://wwp.icq.com/39362285 > \ |_ S _|
Email: < mailto:WTerryLincoln@engineer.com > \ |U|
< http://www.AngelFire.com/ny/TerryLincoln > \ / |S| \
< http://www.geocities.com/Eureka/Concourse/7326 > \ | |
================================================== ~~~~~
Opinions expressed do not represent the management of UTC.
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next reply other threads:[~1999-06-30 22:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-23 6:19 Lincoln, W. Terry [this message]
1999-06-30 22:10 ` Lincoln, W. Terry
-- strict thread matches above, loose matches on Subject: below --
1999-06-22 13:57 John Wiersba
1999-06-22 14:07 ` DJ Delorie
1999-06-30 22:10 ` DJ Delorie
1999-06-30 22:10 ` John Wiersba
1999-06-22 12:09 Lincoln, W. Terry
1999-06-30 22:10 ` Lincoln, W. Terry
1999-06-22 11:57 John Wiersba
1999-06-22 13:41 ` Christopher Faylor
1999-06-30 22:10 ` Christopher Faylor
1999-06-30 22:10 ` John Wiersba
1999-06-21 15:59 Phil Edwards
1999-06-21 16:32 ` Brendan Simon
1999-06-30 22:10 ` Brendan Simon
1999-06-22 11:00 ` itz
1999-06-30 22:10 ` itz
1999-06-30 22:10 ` Phil Edwards
1999-06-21 15:40 John Wiersba
1999-06-30 22:10 ` John Wiersba
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=B3953869CBF8D211A1E50004AC4C1B5402F41A@ultimate2.ultimate.com \
--to=terryl@ultimatetechnology.com \
--cc=cygwin@sourceware.cygnus.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).