Re: Physical path resolution does not handle parent junction points

2019-08-29 Thread Andrey Repin
Greetings, Dan Levi! > Open terminal (as admin): > [~] $ mkdir -p A/B > [~] $ ln -s A C > [~] $ cmd /c "mklink /j D A" > Junction created for D <<===>> A > [~] $ (cd C/B ; pwd -P) > /home/me/A/B > [~] $ (cd D/B ; pwd -P) > /home/me/D/B > The last output should be /home/me/A/B, not /home/me/D/B.

Physical path resolution does not handle parent junction points

2019-08-29 Thread Dan Levi
Open terminal (as admin): [~] $ mkdir -p A/B [~] $ ln -s A C [~] $ cmd /c "mklink /j D A" Junction created for D <<===>> A [~] $ (cd C/B ; pwd -P) /home/me/A/B [~] $ (cd D/B ; pwd -P) /home/me/D/B The last output should be /home/me/A/B, not /home/me/D/B. realpath displays the same behavior. --