On Tue, 2016-10-04 at 10:32 +0300, Angelo Moreschini wrote: > practically you say me to create my own script to realize the connection to > the file (script) locate in /usr/ bin (as an alternative to the creation of > a link). [You're still top-posting. Please stop doing that. It makes the thread much harder to follow] > I understand your idea: this can 'be just an alternative -More "COMPLEX > than to use a link- to get the same result. Not necessarily. A script can do more than a link because it can set up environment variables before calling the target program. > However even before writing the script, I did an experiment > > the file /usr/bin/firefox exists and has execute permission: > [angelo_dev@localhost ~]$ ls -l /usr/bin/firefox > -rwxr-xr-x. 1 root root 6995 Nov 2 2015 /usr/bin/firefox > > *but is is not run :* > [angelo_dev@localhost ~]$ sudo /usr/bin/firefox > [sudo] password for angelo_dev: > Error: /usr/lib64/firefox/firefox not found > /usr/lib/firefox/firefox not found > Why do you need to call firefox using sudo? I presume the errors are caused by sudo's environment not being what Firefox needs. However I still don't understand what your problem actually is so maybe I should just shut up. As I said before I don't use Gnome, so creating a desktop shortcut for that environment is outside my comfort zone. All I meant to say is that if your target binary is for some reason in the wrong place, you can get round it using a script. That's all. poc _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
