A symlink is a symbolic link, and the concept derives from Unix. In> So Win7 supports them, eh? What are they and what does Windows (and MS) call them? *How do I make them?
AFAIK, a Windows junction *is* a symlink, and has been available since> Anyone care to comment on whether or not there are advantages to using symbolic links to a directory rather than junctions, or vice versa??
I've been creating them with 4NT for so long that I couldn't tell you when I started doing so :) and therefore I've never had any need for the Sysinternals tools that do so despite using a number of those tools for other things (4NT/TC has been the first software install on the last dozen new Windows installations I've done for myself, with the Sysinternals Suite about fourth or fifth). Sadly that MS page isn't really up to date and I've not been able to find anything from them that fully documents the differences, hence the question here.What *hasn't* been available is a tool to create them, unless you buy the Win2K Resource Kit
My suspicion is that Windows 7 (at least) removes that restriction because I have Junctions on my C partition that point to the D partition, and the two are on separate disk devices.Junctions are restricted to a single volume, symlinks can cross volume boundaries
Nah, my batch file explicitly uses MKLINK /J (see my post in the thread linked to below).If you have been using MKLINK on Vista or later, you may have been creating symbolic links all along
Sure, but MS breaks these ones (via their ACLs) deliberately, as per Vince's thread here:All file systems which handle symbolic links can have broken links