If I run this command
find $HOME/MySymlinkedPath -name "run*.sh" nothing happens, and gives no error ('MySymlinkedPath' is a symlinked path to another hard drive other then my $HOME one).
These also fails:
find ~/MySymlinkedPath -name "run*.sh" find /home/MyUserName/MySymlinkedPath -name "run*.sh"
And just to make it sure, this non existent path fails (of course)
find $HOME/MySymlinkedPathDUMMYTEST -name "run*.sh" so the path is being found (because that error does not happen) but
find doesn't perform the search on it, and I am a lot clueless now.
It only works if I
cd $HOME/MySymlinkedPath first and remove the path reference like this
find -name "run*.sh" but that is not good for my scripts.
An additional info:
this command works as usual
ls $HOME/MySymlinkedPath/run*.sh, and if I go there
cd $HOME/MySymlinkedPath and run this
ls .. the result is not what I was expecting -- the list of the path where the symlinked path is located -- it returns the list of the real path on the another media/harddrive!!!
pwd -P /media/MediaIdentifier/RealPath pwd /home/MyUser/MySymlinkedPath
Is this a problem with
ls, or with my system? or it is expected and not a problem at all?? I am on Ubuntu 12.10. It fails on all terminals I tested so doesn't seems a terminal "problem".