From: Chris Faylor <cgf@cygnus.com>
To: WTerryLincoln@engineer.com
Cc: "'itz@lbin.com'" <itz@lbin.com>,
"'pedwards@jaj.com'" <pedwards@jaj.com>,
"'cygwin@sourceware.cygnus.com'" <cygwin@sourceware.cygnus.com>,
"'John.Wiersba@medstat.com'" <John.Wiersba@medstat.com>
Subject: Re: question (latest "stable" dll?) + bugs: vim, bash, gcc, cp, f ind, less, zip, ls
Date: Tue, 22 Jun 1999 13:36:00 -0000 [thread overview]
Message-ID: <19990622163728.B29902@cygnus.com> (raw)
In-Reply-To: <B3953869CBF8D211A1E50004AC4C1B5408075C@ultimate2.ultimate.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?
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
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
WARNING: multiple messages have this Message-ID
From: Chris Faylor <cgf@cygnus.com>
To: WTerryLincoln@engineer.com
Cc: "'itz@lbin.com'" <itz@lbin.com>,
"'pedwards@jaj.com'" <pedwards@jaj.com>,
"'cygwin@sourceware.cygnus.com'" <cygwin@sourceware.cygnus.com>,
"'John.Wiersba@medstat.com'" <John.Wiersba@medstat.com>
Subject: Re: question (latest "stable" dll?) + bugs: vim, bash, gcc, cp, f ind, less, zip, ls
Date: Wed, 30 Jun 1999 22:10:00 -0000 [thread overview]
Message-ID: <19990622163728.B29902@cygnus.com> (raw)
Message-ID: <19990630221000.ohDhEhu4T-Oem10cp8ih1SN7pnX7Z9YyLUXaZKdNMqI@z> (raw)
In-Reply-To: <B3953869CBF8D211A1E50004AC4C1B5408075C@ultimate2.ultimate.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?
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
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next prev parent reply other threads:[~1999-06-22 13:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-22 12:09 question (latest "stable" dll?) + bugs: vim, bash, gcc, cp, find, " Lincoln, W. Terry
1999-06-22 13:36 ` Chris Faylor [this message]
1999-06-30 22:10 ` question (latest "stable" dll?) + bugs: vim, bash, gcc, cp, f ind, " Chris Faylor
1999-06-30 22:10 ` question (latest "stable" dll?) + bugs: vim, bash, gcc, cp, find, " Lincoln, W. Terry
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=19990622163728.B29902@cygnus.com \
--to=cgf@cygnus.com \
--cc=John.Wiersba@medstat.com \
--cc=WTerryLincoln@engineer.com \
--cc=cygwin@sourceware.cygnus.com \
--cc=itz@lbin.com \
--cc=pedwards@jaj.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).