Re^2: unable to make manifest with symlinks

modern Windows still lacks the feature

That's not right. Windows 2000 (and later) had junctions and Windows XP (and later) had symlinks.

Comment on Re^2: unable to make manifest with symlinks

Replies are listed 'Best First'.
Re^3: unable to make manifest with symlinks by soonix (Canon) on Oct 24, 2019 at 17:27 UTC
True, but because of Windows' usage of file type as part of the file name, its ".lnk" files are still different from Unix' symlinks.	[reply]
Re^4: unable to make manifest with symlinks by jcb (Parson) on Oct 24, 2019 at 23:57 UTC
No, ".lnk" files are shell links; those go back to Windows 95.	[reply]
Re^3: unable to make manifest with symlinks by jcb (Parson) on Oct 25, 2019 at 00:01 UTC
Interesting, yet they are either rarely used or not really what they look like. I am not surprised that NTFS has added such features, but I am fairly sure that there are limitations. If I recall correctly, junctions can only refer to directories and are more like Linux's bind mounts than POSIX symlinks or hardlinks, including a requirement for special privilege to create them. If XP added true symlinks, what are the commands for using them? I doubt that `ln -s` works...	[reply]
Re^4: unable to make manifest with symlinks by daxim (Curate) on Oct 25, 2019 at 07:41 UTC
what are the commands for using them? mklink, fsutil, ln (in the Windows Resource Kit), ln (3rd party)	[reply]
Re^5: unable to make manifest with symlinks by jcb (Parson) on Oct 25, 2019 at 23:45 UTC
And I will guess no support in the GUI file manager, which is all that most Windows users use, so the feature is basically useless to the vast majority of Windows users. :-/	[reply]