This is the mail archive of the
mailing list for the Cygwin project.
Re: Symbol link trouble ?
- To: cygwin at cygwin dot com
- Subject: Re: Symbol link trouble ?
- From: Pierre Muller <muller at cerbere dot u-strasbg dot fr>
- Date: Wed, 25 Apr 2001 17:16:40 +0200
>On Wed, Apr 25, 2001 at 02:09:48PM +0200, Pierre Muller wrote:
>> At 13:13 25/04/01 , vous avez écrit:
> > >Could be a buffering technique of W95. I have just read the Microsoft
> >KB article Q128932 "How Windows 95 Resolves Shortcut Links" but it
> >doesn't obtain any additional information.
> Using strace seems to indicate that the file test.h.lnk is read!
>Sure it's read. Cygwin doesn't see if the file is actually read or
>if the file content is read from an already existing OS buffer.
>> Should I send you the binary link file and the strace output.
>Actually I have no hope to find something strange from the strace
>but it doesn't hurt. Send the strace (not the link file which
>is useless to me) as gzipped attachment to mailto:email@example.com.
You are probably right:
there is no read after the call to CreateFileA
for the symlink disk file)
I now tested it by first setting the link in the Windows explorer (WE)
and testing this, I found out the following:
setting a link with WE works for cygwin bash
it simply reports the win32 path of the target file.
Changing it with WE works normally and is reflected correctly.
But removing the file in bash are setting it to another
target makes the windows link reappear unchanged !
Note that if remove the link from inside WE then
the subsequent call to ln works correctly
(the link is to the corrct file,
but in WE I still get no target file written !)
It seems like WE is doing something more than just deleting
the test.h.lnk disk file !
Institut Charles Sadron
F 67083 STRASBOURG CEDEX (France)
Phone : (33)-3-88-41-40-07 Fax : (33)-3-88-41-40-99
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple