Greetings, L A Walsh!
> Andrey Repin wrote:
>> I would argue against all junctions being treated blindly.
>> The difference with bind mounts in Linux is that in Linux
>> you don't have the
>> information available within the filesystem itself, and have
>> no other option,
>> than to treat them as regular directories.
>> Only direct volume junctions cause an issue, and this is what
>> should be fixed,
>> if possible, not sidetracked with questionable workarounds.
> ----
> Could you describe the benefits of your proposed solution?
> You do know that MS originally called junctions "mountpoints",
> right? So why would cygwin treating them as such be a "questionable
> workaround"?
How they are called, and how they behave is a two different questions.
> How would you want to treat them?
Easy way: As symlinks, just like now, unless it's a volume mount point that
can't be normalized to a disk letter.
Preferred way: Fix volume mounts accessibility
\\?\{UUID} -> /dev/disk/by-uuid/UUID
--
With best regards,
Andrey Repin
Friday, March 10, 2017 16:10:57
Sorry for my terrible english...
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
