[Octave-bug-tracker] [bug #44814] which and run fail on windows for new files

[Philip Nienhuis]

Follow-up Comment #7, bug #44814 (project octave):

Some background (but I am no expert, this is just from my own experience):
AFAIK NTFS junctions and (sym|hard)links weren't really meant for normal
users, at least until fairly recently; but rather for sysadmins to enable them
to manage a.o., distributed file systems. 
There are quite a few varieties of these "links", each with their own pros and
cons, each depending on Windows and NTFS versions.
So I'm not surprised that Octave/MSYS/mingw functions have problems there, and
I'm especially unsure if it's realistic to pursue exact *nix-like behavior. If
it can be done at all it might only work on the most recent NTFS versions
(i.e., Windows versions).

A little more info is e.g., here:
http://www.howtogeek.com/howto/16226/complete-guide-to-symbolic-links-symlinks-on-windows-or-linux/
here:
http://stackoverflow.com/questions/9042542/what-is-the-difference-between-ntfs-junction-points-and-symbolic-links
and from my old bookmark collection:
https://support.microsoft.com/en-us/kb/205524/   and 
https://technet.microsoft.com/en-us/sysinternals/bb896768.aspx
(but none of these explicitly touch upon the differences between
NTFS/driver/Windows versions)


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?44814>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/