[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Windows symbolic links (was: Re: Shared files between projects)

From: Kenneth Porter <shiva_at_sewingwitch.com>
Date: Mon, 07 Jan 2008 12:44:20 -0800

On Monday, January 07, 2008 11:14 AM -0500 Andy Levy <andy.levy_at_gmail.com>

>> Windows has something like a symlink, but I don't think Subversion has
>> the ability to use it. Perhaps open a feature request for it.
>> <http://en.wikipedia.org/wiki/NTFS_symbolic_link>
> The more desirable option as it is most like UNIX symlinks. But leaves
> non-Vista/Server2K8 users out in the cold.
>> <http://en.wikipedia.org/wiki/NTFS_junction_point>
> Is fraught with warnings, odd behaviors & "not safe for..."

>From the information in the wiki article, it appears that the risks involve
the awareness of the various shells (both GUI and command line), and not
the underlying junction point. The question is whether a given operation
operates on the JP or the object it points to. Unix users have used
symlinks for a long time and so are mostly aware of which tools affect them
and how. If you use a JP in Windows, you need to have the same awareness.

To me, a JP looks more like a loop mount in Linux.

It's not clear why MS chose to make the Vista symbolic link accessible only
to Administrators.

It looks like JP's only work for directories, not files.

>From <http://en.wikipedia.org/wiki/NTFS>

> Symbolic links were introduced in Windows Vista.[22] Symbolic links (or
> Soft links) are resolved on the client side. So when a symbolic link is
> shared, the target is subject to the access restrictions on the client,
> and not the server.


To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-01-07 21:44:58 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.