Added some interesting functionality to my cygwin sandbox

Christopher Faylor
Wed Jul 2 15:25:00 GMT 2003

On Wed, Jul 02, 2003 at 11:15:33AM -0400, Igor Pechtchanski wrote:
>Why?  I just tried it on Linux, and could not create a symlink to an empty
>path.  If we added some logic to link processing code in Cygwin to revert
>to the Win32 path if the POSIX path is empty, I don't see any reason why
>this woulnd't work...  It won't even be a slowdown for normal symlinks,
>since we'd only do this bit of logic if we failed to open the POSIX path.

I really like this idea.  Corinna?  The symlink stuff is your code.  What
do you think?

(Of course, you can *always* use the mount table for all of this.  I wonder
if we should just be using the mount table here.)

>> But as we're trying to get around a problem with cymlink destinations
>> how about having an internal name like the cygdrive prefix? That way we
>> could guarentee that it would point to the correct location.
>Yeah, that's the previously suggested alternative.  However, I'm wary of
>any hard-coded valid paths...  Corinna's idea is basically that, but with
>the path that's normally invalid.

Anything which uses a hard-coded path pollutes the name space.  I'd
rather avoid that.


More information about the Cygwin-developers mailing list