This is the mail archive of the cygwin@sources.redhat.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: [ANNOUNCEMENT]: Important change to symbolic link functionali ty


> >
> >If you create a symlink that points to an object and spans a mount
> >entry, both the "cygwin" path and the "dos" path will 'do the right
> >thing' and point where you think they should.
> >
> >Then, change the underlying mount entry.
> >
> >The "cygwin" path will point to the new location (since it is
> >interpreted using the new mount entry) but the "dos" path will still
> >point to the old (possibly non-existant, now) location because it *was*
> >interpreted at symlink-creation-time using the old mount table.
> >
> >IMO, this slight and rare inconvenience is worth the price -- at least
> >now, symlinks will mostly work from Explorer.  Let's be honest, now: how
> >often do you really rearrange your mount table?
> 
> I don't change my mount table very often but this is still potentially
> very surprising behavior for a user.  I don't think we should dismiss
> it lightly, as much as I like the idea of using .lnk files.
> 

Guess what happens when you rename a directory that a shortcut is
dependent upon in Win32?  I think a documentation entry would suffice. 
Perhaps some tool, perhaps even mount, could take care of modifying the
.lnk files with absolute paths in them after a move of the mount point.

Earnie.

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]