Timeline for answer to node.js conflicts: /sbin/node vs /usr/bin/node by Aust
Current License: CC BY-SA 3.0
Post Revisions
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 15, 2017 at 3:23 | comment | added | mtraceur |
Symlinking at a new location almost certainly needs a hash node invocation in your existing terminals, because modern shells remember the location of commands that have been previously looked up in PATH. The hash builtin command in such shells tells them to redo the lookup, and remember the new location.
|
|
| Dec 12, 2014 at 3:08 | comment | added | Deepak Joy Cheenath |
@Leftium: You also need to run: source ~/.bashrc to reload the .bashrc file (if you want to avoid restarting the terminal) read more..
|
|
| Jul 16, 2013 at 22:36 | comment | added | Leftium | When I created a symlink, it did not work until I started another terminal. Try restarting your terminal... or my answer that works without symlinks/aliases ^^ | |
| Mar 21, 2013 at 17:51 | review | First posts | |||
| Mar 21, 2013 at 17:57 | |||||
| Mar 21, 2013 at 17:33 | history | answered | Aust | CC BY-SA 3.0 |