Unless you are executing from a directory that is in your path, you need to preceed the name of the bin with "./". You can add directories to you path in /etc/profile. For instance, a kde user might want to append /opt/kde/bin to his path declaration. Unless you have a directory with several bins that you execute frequently that is outside your path, then it makes more sense to symlink the bins you want to execute to directories that are in your path. For instance, you have realplayer in /opt/rvplayer say. Instead of ham-fistedly cp'ing it to a directory in your path, you could "ln -s /opt/rvplayer/rvplayer /usr/X11R6/bin/rvplayer" That way if any other program depends on that app being in /opt/rvplayer it can still find it, and with rvplayer symlinked you can now just type "rvplayer" without the ./ from an rxvt or xterm. Joseph Beaman wrote:
Thanks--that works beautifully. Now my next question is WHY do you have to do that?
- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e