Comment 2 for bug 1812768

Many thanks. Appreciate the quick response.

I totally agree that it would be unreasonable to actually invoke some executable code to accomplish reading a file off of the filesystem.
In my mind, the main purpose of ntfs-3g (and any FS driver) is to at a minimum provide a view into the content on the mounted filesystem.

That being the case, I suppose what I would expect to be able to do here in the case of the "executable link" is:
1) Have it manifest itself as a normal file, with the content being the reparse point byte content
2) Have it manifest itself as a broken symlink to the URL target
I can see how both of those don't do justice to the actual reparse point itself, however (at least in my case) I think either of those would ideally be a better "default".

Practically, what would the EREMOTE plugin you proposed do? Would that just return a more specific error rather than "unsupported reparse point"? If my two options above don't make any sense to implement, I like the idea of having a more specific error for general users encountering this type of thing, especially if we could include the target in the message.