Tag Info

New answers tagged


In general, the evironment variable $PATH specifies the directories in which to look when executing a command. From the official manual: When you type a command to run, the system looks for it in the directories specified by PATH in the order specified You can add directories to $PATH with export PATH="/path/to/executable":$PATH. Note that the : serves ...


Since your path has spaces in it you need to enclose both the path AND the variable in "". Try this from the command line. export week4="/home/Justin/Week 4/assignment/" Now you should be able to navigate to that directory by typing cd $week4 If you want to make this permanent then add the same line to your .bashrc file.


/ is the very top of your filesystem. If you type cd /home/directory, you can do that from anywhere, because it is the full path. If you type cd home/directory, that will only work if you are in location /, similarly, if you are in /home, you could type cd directory, but not cd /directory (because that doesn't exist, it's either /home/directory, or just ...


Make your preferred path first: PATH=/opt/msp430-47/bin:$PATH Check it echo $PATH Fix permissions sudo find /opt/msp430-47 -type d -exec chmod +rx "{}" \; sudo chmod -R +rx /opt/msp430-47/bin


@ John: I believe you need to check your /etc/xrdpstartwm.sh - the first lines in mine reads, if [ -f /etc/X11/xinit/xinitrc ] then . /etc/X11/xinit/xinitrc exit 0 fi** That means that if /etc/X11xinit/xinitrc exists, that file will be executed instead - and it won't help much to add the . /etc/environment to /etc/xrdpstartwm.sh. :-) /Per ...


A few days ago I was satisfied with my answer. I also knew that the which command is not used to test whether a command exists. Now I'm not so satisfied with my answer, and I refer to this great response. With a simple which command: which foo.sh Or a type command: type foo.sh And you can influence this with the order of the paths in your $PATH or ...

Top 50 recent answers are included