You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Adam Aulick <ad...@aulick.net> on 2006/04/13 21:33:02 UTC

NTFS Junction points (symlinks) within the working copy

I have a directory hierarchy on an NTFS volume on a Windows machine,  
which contains junction points (symlinks) linked to other locations  
within the same directory.  If I svn import this hierarchy, and then  
checkout to some other location on the disk, the working copy has  
duplicate subdirectories, instead of links.

I don't know how to tell whether the links are getting broken on the  
import, or on the checkout.  Is there a way to make this work?

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: NTFS Junction points (symlinks) within the working copy

Posted by Nico Kadel-Garcia <nk...@comcast.net>.
Adam Aulick wrote:
> On Apr 13, 2006, at 5:40 PM, Nico Kadel-Garcia wrote:
>
>> NTFS supports shortcuts, *NOT* symlinks.
>
> This is a common misconception.  Shortcuts are regular files treated
> specially by Explorer.exe.  NTFS supports what Microsoft calls
> "Junction Points" or "Reparse Points" which can act as symlinks (on
> directories) or hard links (on files).  Unfortunately, practically no
> windows executables can tell the difference between a symlink and a
> regular directory, which leads to unfortunate behavior like Windows
> Explorer recursively deleting the target directory instead of just
> unlinking the junction point.  And, apparently, subversion screwing
> up my directory hierarchy.
>
> There's a good windows shell extension NTFS Link <http://
> www.elsdoerfer.info/ntfslink/> that causes Explorer.exe to behave
> more reasonably when dealing with junction points.

Then they're not exactly symlinks: similar, but with some really unfortunate 
behaviors. Ouch.

>> I suspect that you will never be able to get this to work the way
>> you expect.
>
> On this point you may be right.

Yeah, even the Wiki about it at 
http://www.realclimate.org/index.php/archives/2006/04/lindzen-point-by-point/ 
warns of various weirdnesses of them.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

RE: NTFS Junction points (symlinks) within the working copy

Posted by Mark Johnson <mj...@sightworks.com>.
Hardlinks and Symbolic Links (Junctions) have been part of windows OS
since Windows 2000.  Junctions can span hardrives and partitions and may
only refer to directories.  Hardlinks cannot span different disks or
partitions.

I use the NTFS Link all the time, and I really think that subversion
should support Hardlinks and Junctions on windows.  

-----Original Message-----
From: Adam Aulick [mailto:adam@aulick.net] 
Sent: Thursday, April 13, 2006 4:04 PM
To: Nico Kadel-Garcia
Cc: users@subversion.tigris.org
Subject: Re: NTFS Junction points (symlinks) within the working copy


On Apr 13, 2006, at 5:40 PM, Nico Kadel-Garcia wrote:

> NTFS supports shortcuts, *NOT* symlinks.

This is a common misconception.  Shortcuts are regular files treated  
specially by Explorer.exe.  NTFS supports what Microsoft calls  
"Junction Points" or "Reparse Points" which can act as symlinks (on  
directories) or hard links (on files).  Unfortunately, practically no  
windows executables can tell the difference between a symlink and a  
regular directory, which leads to unfortunate behavior like Windows  
Explorer recursively deleting the target directory instead of just  
unlinking the junction point.  And, apparently, subversion screwing  
up my directory hierarchy.

There's a good windows shell extension NTFS Link <http:// 
www.elsdoerfer.info/ntfslink/> that causes Explorer.exe to behave  
more reasonably when dealing with junction points.

> I suspect that you will never be able to get this to work the way  
> you expect.

On this point you may be right.



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: NTFS Junction points (symlinks) within the working copy

Posted by Adam Aulick <ad...@aulick.net>.
On Apr 13, 2006, at 5:40 PM, Nico Kadel-Garcia wrote:

> NTFS supports shortcuts, *NOT* symlinks.

This is a common misconception.  Shortcuts are regular files treated  
specially by Explorer.exe.  NTFS supports what Microsoft calls  
"Junction Points" or "Reparse Points" which can act as symlinks (on  
directories) or hard links (on files).  Unfortunately, practically no  
windows executables can tell the difference between a symlink and a  
regular directory, which leads to unfortunate behavior like Windows  
Explorer recursively deleting the target directory instead of just  
unlinking the junction point.  And, apparently, subversion screwing  
up my directory hierarchy.

There's a good windows shell extension NTFS Link <http:// 
www.elsdoerfer.info/ntfslink/> that causes Explorer.exe to behave  
more reasonably when dealing with junction points.

> I suspect that you will never be able to get this to work the way  
> you expect.

On this point you may be right.



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: NTFS Junction points (symlinks) within the working copy

Posted by Nico Kadel-Garcia <nk...@comcast.net>.
Adam Aulick wrote:
> I have a directory hierarchy on an NTFS volume on a Windows machine,
> which contains junction points (symlinks) linked to other locations
> within the same directory.  If I svn import this hierarchy, and then
> checkout to some other location on the disk, the working copy has
> duplicate subdirectories, instead of links.
>
> I don't know how to tell whether the links are getting broken on the
> import, or on the checkout.  Is there a way to make this work?

NTFS supports shortcuts, *NOT* symlinks. I suspect that you will never be 
able to get this to work the way you expect. 


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org