How the Windows Subsystem for Linux Redirects Syscalls

Re:How the Windows Subsystem for Linux Redirects Syscalls by mmebane on Wednesday June 08, 2016 @04:57PM (#11865606)

> `mklink` [0] has existed since Windows Vista for NTFS file system. No settings toggling required.

There are several limitations in the Windows/NTFS implementation, however:

1. You have to specify the target type (file or directory) at link creation time.

2. Creating symbolic links requires either being an Administrator user, or having the "Create symbolic links" group policy enabled for your account.

3. No real directory hard links. (EDIT: For some reason, I forgot that Linux doesn't have these, either. Maybe I was thinking of bind mounts.)

[ Parent | on HN ]

Re:How the Windows Subsystem for Linux Redirects Syscalls by dsp1234 on Wednesday June 08, 2016 @05:11PM (#11865700)

3. No real directory hard links. Junction points are close, but still distinguishable from

Windows isn't the only OS that disallows creating directory hard links.

[ Parent | on HN ]

Re:How the Windows Subsystem for Linux Redirects Syscalls by mmebane on Wednesday June 08, 2016 @05:34PM (#11865859)

Huh, I wonder why I misremembered that. Thanks for the correction.

[ Parent | on HN ]