View Single Post
Old 02-27-2016, 03:37 PM   #27321
DMcCunney
New York Editor
DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.
 
DMcCunney's Avatar
 
Posts: 6,384
Karma: 16540415
Join Date: Aug 2007
Device: PalmTX, Pocket eDGe, Alcatel Fierce 4, RCA Viking Pro 10, Nexus 7
Quote:
Originally Posted by CRussel View Post
Hard links have always been supported on NTFS, but until mklink was added as an internal command to cmd.exe, there was no native way to implement them.
Like I said, not exposed by default. IIRC, back when you had to install an optional MS package to get mklink.

Quote:
OpenNT and Interix could create them, and then they were visible and supported on Windows. Now they are fully supported by PowerShell, with New-Item. Which supports hard and symbolic links, as well as junctions.
I'm not surprised PowerShell supports them. (I'd be surprised if it didn't.) I make a fair bit of use of them, but through the aforementioned LSE.
______
Dennis

Last edited by DMcCunney; 02-29-2016 at 08:53 AM.
DMcCunney is offline   Reply With Quote