Welcome!

By registering with us, you'll be able to discuss, share and private message with other members of our community.

SignUp Now!

How to? Directory symbolic links vs directory junctions

Jul
68
1
The MKLINK command offers options to create a junction or a symbolic link (as well as hard links). When it comes to directories, what's the difference between creating a symbolic link vs creating a junction (other than the fact that you need to be in an elevated session to create symlinks)? Always wondered about this.

Mark E.
 
I found this at superuser.com. I cannot vouch for its accuracy.

1661031008309.png
 
Junction Links and Symbolic Links seem to have similar features. But there are some noticeable differences and they are as follows:

Junction LinksSymbolic Links
Introduced in Windows 2000 OS and compatible to Windows with Windows 2000 and beyond.Introduced with Windows Vista and Windows Server 2008. So, compatible with Windows those OS and beyond.
Junction Links works only for directories.Symbolic Links works for both directories and files.
Junctions links work only for the absolute path.Symbolic Links works for both absolute and relative path.
Junction Links works for the local drives volumes and partition onlySymbolic Links works for local as well as remote paths.
Creating junction links does not require any special permissions, and Windows Standard User is sufficient. As a result, we can say it has a low-security profile.Creating Symbolic Links requires Administrator privileges. Therefore it has high-security profiles.
It is a legacy Links type created for the NTFS file system.It is modern links types and was developed to support migration and application compatibility with UNIX operating systems.
 
More info in regards to symbolic links, directory junctions, and such, is available from;

NTFS links on Wikipedia.

Joe
 
I noticed that MS office produce will open a symbolically linked file, but save it as a real file breaking the link.
 
Back
Top
[FOX] Ultimate Translator
Translate