How can this happen?
jon@vaio:~/brickify$ /usr/bin/node -v
v0.8.11
jon@vaio:~/brickify$ echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
jon@vaio:~/brickify$ node -v
jon@vaio:~/brickify$
/usr/bin
is in $PATH
, so just writing node -v
should work the same as writing /usr/bin/node -v
node
exist in any other folder on the path?which node
will show you the path of the binary that's actually running when you donode
without an absolute path. Like ObsessiveFOSS says, it's likely there's anothernode
in the directories before/usr/bin
./usr/sbin
... When I run/usr/sbin/node -v
I get the same lack of output as when I runnode -v
. So that explains. But, why the node installation chose to set things up this way, still puzzles me. But that's another question. @roadmr:which node
points to/usr/bin
@MartyFried: The dollar sign was a typo