Running a program from terminal, “command not found”

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP








up vote
2
down vote

favorite












I'm new to Ubuntu, and trying to start opening and running programs directly from the terminal. I've tried this multiple times with different programs, and always get the same error -- "command not found". I've tried running programs both from the main directory and from the sub-folder the program is in, but neither work.



Any tips?



Here's what I've been getting:



When I try running in the folder:



Julia@a-capella: ~Documents/events_adc$ nuetrino_s1_1
nuetrino_s1_1: command not found


When I try running from the main directory:



ulia@a-capella: ~$ nuetrino_s1_1
nuetrino_s1_1: command not found


Oddly enough, firefox (and no other programs I've tried) will run from here.



Thanks!






command-line







share|improve this question



















  • 4




    If you type the command echo $PATH it will display your command path; ie. where commands are searched. Your current directory would be shown as a "." if its there (i very much doubt it) which is what you're probably missing. The easiest way to run commands in your current directory is "./nuetrino_s1_1" (the './ ' part tells the system to look for it in the current directory {or $PWD])
    – guiverc
    Feb 8 at 22:18











  • My guess is that - the file must have executable permissions to be executed.
    – pa4080
    Feb 8 at 22:44














up vote
2
down vote

favorite












I'm new to Ubuntu, and trying to start opening and running programs directly from the terminal. I've tried this multiple times with different programs, and always get the same error -- "command not found". I've tried running programs both from the main directory and from the sub-folder the program is in, but neither work.



Any tips?



Here's what I've been getting:



When I try running in the folder:



Julia@a-capella: ~Documents/events_adc$ nuetrino_s1_1
nuetrino_s1_1: command not found


When I try running from the main directory:



ulia@a-capella: ~$ nuetrino_s1_1
nuetrino_s1_1: command not found


Oddly enough, firefox (and no other programs I've tried) will run from here.



Thanks!






command-line







share|improve this question



















  • 4




    If you type the command echo $PATH it will display your command path; ie. where commands are searched. Your current directory would be shown as a "." if its there (i very much doubt it) which is what you're probably missing. The easiest way to run commands in your current directory is "./nuetrino_s1_1" (the './ ' part tells the system to look for it in the current directory {or $PWD])
    – guiverc
    Feb 8 at 22:18











  • My guess is that - the file must have executable permissions to be executed.
    – pa4080
    Feb 8 at 22:44












up vote
2
down vote

favorite









up vote
2
down vote

favorite











I'm new to Ubuntu, and trying to start opening and running programs directly from the terminal. I've tried this multiple times with different programs, and always get the same error -- "command not found". I've tried running programs both from the main directory and from the sub-folder the program is in, but neither work.



Any tips?



Here's what I've been getting:



When I try running in the folder:



Julia@a-capella: ~Documents/events_adc$ nuetrino_s1_1
nuetrino_s1_1: command not found


When I try running from the main directory:



ulia@a-capella: ~$ nuetrino_s1_1
nuetrino_s1_1: command not found


Oddly enough, firefox (and no other programs I've tried) will run from here.



Thanks!






command-line







share|improve this question















I'm new to Ubuntu, and trying to start opening and running programs directly from the terminal. I've tried this multiple times with different programs, and always get the same error -- "command not found". I've tried running programs both from the main directory and from the sub-folder the program is in, but neither work.



Any tips?



Here's what I've been getting:



When I try running in the folder:



Julia@a-capella: ~Documents/events_adc$ nuetrino_s1_1
nuetrino_s1_1: command not found


When I try running from the main directory:



ulia@a-capella: ~$ nuetrino_s1_1
nuetrino_s1_1: command not found


Oddly enough, firefox (and no other programs I've tried) will run from here.



Thanks!






command-line




command-line






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Feb 8 at 22:19









N0rbert

16.6k33479




16.6k33479










asked Feb 8 at 22:12









Julia Book

1613




1613







  • 4




    If you type the command echo $PATH it will display your command path; ie. where commands are searched. Your current directory would be shown as a "." if its there (i very much doubt it) which is what you're probably missing. The easiest way to run commands in your current directory is "./nuetrino_s1_1" (the './ ' part tells the system to look for it in the current directory {or $PWD])
    – guiverc
    Feb 8 at 22:18











  • My guess is that - the file must have executable permissions to be executed.
    – pa4080
    Feb 8 at 22:44












  • 4




    If you type the command echo $PATH it will display your command path; ie. where commands are searched. Your current directory would be shown as a "." if its there (i very much doubt it) which is what you're probably missing. The easiest way to run commands in your current directory is "./nuetrino_s1_1" (the './ ' part tells the system to look for it in the current directory {or $PWD])
    – guiverc
    Feb 8 at 22:18











  • My guess is that - the file must have executable permissions to be executed.
    – pa4080
    Feb 8 at 22:44







4




4




If you type the command echo $PATH it will display your command path; ie. where commands are searched. Your current directory would be shown as a "." if its there (i very much doubt it) which is what you're probably missing. The easiest way to run commands in your current directory is "./nuetrino_s1_1" (the './ ' part tells the system to look for it in the current directory {or $PWD])
– guiverc
Feb 8 at 22:18





If you type the command echo $PATH it will display your command path; ie. where commands are searched. Your current directory would be shown as a "." if its there (i very much doubt it) which is what you're probably missing. The easiest way to run commands in your current directory is "./nuetrino_s1_1" (the './ ' part tells the system to look for it in the current directory {or $PWD])
– guiverc
Feb 8 at 22:18













My guess is that - the file must have executable permissions to be executed.
– pa4080
Feb 8 at 22:44




My guess is that - the file must have executable permissions to be executed.
– pa4080
Feb 8 at 22:44










1 Answer
1






active

oldest

votes

















up vote
1
down vote



accepted










If you type the command



echo $PATH


it will display your command path, or where commands are searched for. Your current directory would be shown as a "." if its there (i very much doubt it) which is what you're probably missing.



The easiest way to run commands in your current directory is:



./nuetrino_s1_1


The ./ part tells the system to look for the command in the current directory [or $PWD, or present.working.directory].






share|improve this answer






















  • You can add "." to your $PATH (so it searches your present.working.directory for commands) which at first feels great as you no longer have to type "./command", but in my experience you'll keep tripping over it on other machines that don't do it; so you'll end up typing "./command" even if "." is in path. ie. my 2c is just learn to type ./command
    – guiverc
    Feb 8 at 22:32







  • 1




    Adding "." to $PATH is a really BAD idea. It allows all kind of attacks to happen (for exemple : if you put it first, anyone can hijack your session by having a "ls" or other program in a directory you happen to be in. Or even if you put it last, having common typos program there ("sl" "gerp" etc). And there are many other bad security side effects in addition to those. Do NOT put "." in your $PATH.
    – Olivier Dulac
    Mar 23 at 17:49











Your Answer







StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "89"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1004373%2frunning-a-program-from-terminal-command-not-found%23new-answer', 'question_page');

);

Post as a guest

















1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
1
down vote



accepted










If you type the command



echo $PATH


it will display your command path, or where commands are searched for. Your current directory would be shown as a "." if its there (i very much doubt it) which is what you're probably missing.



The easiest way to run commands in your current directory is:



./nuetrino_s1_1


The ./ part tells the system to look for the command in the current directory [or $PWD, or present.working.directory].






share|improve this answer






















  • You can add "." to your $PATH (so it searches your present.working.directory for commands) which at first feels great as you no longer have to type "./command", but in my experience you'll keep tripping over it on other machines that don't do it; so you'll end up typing "./command" even if "." is in path. ie. my 2c is just learn to type ./command
    – guiverc
    Feb 8 at 22:32







  • 1




    Adding "." to $PATH is a really BAD idea. It allows all kind of attacks to happen (for exemple : if you put it first, anyone can hijack your session by having a "ls" or other program in a directory you happen to be in. Or even if you put it last, having common typos program there ("sl" "gerp" etc). And there are many other bad security side effects in addition to those. Do NOT put "." in your $PATH.
    – Olivier Dulac
    Mar 23 at 17:49















up vote
1
down vote



accepted










If you type the command



echo $PATH


it will display your command path, or where commands are searched for. Your current directory would be shown as a "." if its there (i very much doubt it) which is what you're probably missing.



The easiest way to run commands in your current directory is:



./nuetrino_s1_1


The ./ part tells the system to look for the command in the current directory [or $PWD, or present.working.directory].






share|improve this answer






















  • You can add "." to your $PATH (so it searches your present.working.directory for commands) which at first feels great as you no longer have to type "./command", but in my experience you'll keep tripping over it on other machines that don't do it; so you'll end up typing "./command" even if "." is in path. ie. my 2c is just learn to type ./command
    – guiverc
    Feb 8 at 22:32







  • 1




    Adding "." to $PATH is a really BAD idea. It allows all kind of attacks to happen (for exemple : if you put it first, anyone can hijack your session by having a "ls" or other program in a directory you happen to be in. Or even if you put it last, having common typos program there ("sl" "gerp" etc). And there are many other bad security side effects in addition to those. Do NOT put "." in your $PATH.
    – Olivier Dulac
    Mar 23 at 17:49













up vote
1
down vote



accepted







up vote
1
down vote



accepted






If you type the command



echo $PATH


it will display your command path, or where commands are searched for. Your current directory would be shown as a "." if its there (i very much doubt it) which is what you're probably missing.



The easiest way to run commands in your current directory is:



./nuetrino_s1_1


The ./ part tells the system to look for the command in the current directory [or $PWD, or present.working.directory].






share|improve this answer














If you type the command



echo $PATH


it will display your command path, or where commands are searched for. Your current directory would be shown as a "." if its there (i very much doubt it) which is what you're probably missing.



The easiest way to run commands in your current directory is:



./nuetrino_s1_1


The ./ part tells the system to look for the command in the current directory [or $PWD, or present.working.directory].







share|improve this answer














share|improve this answer



share|improve this answer








edited Feb 8 at 22:48









dessert

20k55795




20k55795










answered Feb 8 at 22:27









guiverc

3,72811422




3,72811422











  • You can add "." to your $PATH (so it searches your present.working.directory for commands) which at first feels great as you no longer have to type "./command", but in my experience you'll keep tripping over it on other machines that don't do it; so you'll end up typing "./command" even if "." is in path. ie. my 2c is just learn to type ./command
    – guiverc
    Feb 8 at 22:32







  • 1




    Adding "." to $PATH is a really BAD idea. It allows all kind of attacks to happen (for exemple : if you put it first, anyone can hijack your session by having a "ls" or other program in a directory you happen to be in. Or even if you put it last, having common typos program there ("sl" "gerp" etc). And there are many other bad security side effects in addition to those. Do NOT put "." in your $PATH.
    – Olivier Dulac
    Mar 23 at 17:49

















  • You can add "." to your $PATH (so it searches your present.working.directory for commands) which at first feels great as you no longer have to type "./command", but in my experience you'll keep tripping over it on other machines that don't do it; so you'll end up typing "./command" even if "." is in path. ie. my 2c is just learn to type ./command
    – guiverc
    Feb 8 at 22:32







  • 1




    Adding "." to $PATH is a really BAD idea. It allows all kind of attacks to happen (for exemple : if you put it first, anyone can hijack your session by having a "ls" or other program in a directory you happen to be in. Or even if you put it last, having common typos program there ("sl" "gerp" etc). And there are many other bad security side effects in addition to those. Do NOT put "." in your $PATH.
    – Olivier Dulac
    Mar 23 at 17:49
















You can add "." to your $PATH (so it searches your present.working.directory for commands) which at first feels great as you no longer have to type "./command", but in my experience you'll keep tripping over it on other machines that don't do it; so you'll end up typing "./command" even if "." is in path. ie. my 2c is just learn to type ./command
– guiverc
Feb 8 at 22:32





You can add "." to your $PATH (so it searches your present.working.directory for commands) which at first feels great as you no longer have to type "./command", but in my experience you'll keep tripping over it on other machines that don't do it; so you'll end up typing "./command" even if "." is in path. ie. my 2c is just learn to type ./command
– guiverc
Feb 8 at 22:32





1




1




Adding "." to $PATH is a really BAD idea. It allows all kind of attacks to happen (for exemple : if you put it first, anyone can hijack your session by having a "ls" or other program in a directory you happen to be in. Or even if you put it last, having common typos program there ("sl" "gerp" etc). And there are many other bad security side effects in addition to those. Do NOT put "." in your $PATH.
– Olivier Dulac
Mar 23 at 17:49





Adding "." to $PATH is a really BAD idea. It allows all kind of attacks to happen (for exemple : if you put it first, anyone can hijack your session by having a "ls" or other program in a directory you happen to be in. Or even if you put it last, having common typos program there ("sl" "gerp" etc). And there are many other bad security side effects in addition to those. Do NOT put "." in your $PATH.
– Olivier Dulac
Mar 23 at 17:49


















 

draft saved


draft discarded















































 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1004373%2frunning-a-program-from-terminal-command-not-found%23new-answer', 'question_page');

);

Post as a guest
































































-

Popular posts from this blog

pylint3 and pip3 broken

Image
Clash Royale CLAN TAG #URR8PPP up vote 0 down vote favorite I have tried sudo apt remove --purge on various packages. I get the same when I reinstall. I have also tried reinstall using aptitude. This does not work. My current workaround is to run pylint3 as root, which works, but is bad practice. pip3 $ pip3 Traceback (most recent call last): File "/usr/lib/python3/dist-packages/pip/_vendor/__init__.py", line 33, in vendored __import__(vendored_name, globals(), locals(), level=0) ImportError: No module named 'pip._vendor.pkg_resources' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/bin/pip3", line 9, in <module> from pip import main File "/usr/lib/python3/dist-packages/pip/__init__.py", line 13, in <module> from pip.exceptions import InstallationError, CommandError, PipError File "/usr/lib/python3/dist-packages/pip/exceptions.py", line 6, ...
Read more

Missing snmpget and snmpwalk

Image
Clash Royale CLAN TAG #URR8PPP up vote 0 down vote favorite I have installed Zabbix appliance, directly preinstalled and found that there is missing snmpwalk and snmpget commands. I tried to install it with: apt-get install net-snmp-utils but I have error message: Unable to locate package. I have also check what from SNMP is preinstalled and there is: libsnmp-base libsnmp30:amd64 snmp-mibs-downloader snmpd snmptrapd snmptrapfmt How can I install snmpget and snmpwalk ? snmp zabbix share | improve this question edited Jan 29 at 10:10 Yaron 8,552 7 18 38 asked Jan 29 at 9:51 Alfista 1 apt install snmp perhaps ? If named differently - apt cache snmp – fugitive Jan 29 at 10:00 add a comment  |  up vote 0 down vote favorite I have installed Zabbix appliance, directly preinstalled and found that there is missing snmpwalk and snmpget commands. I tried...
Read more

How to enroll fingerprints to Ubuntu 17.10 with VFS491

Image
Clash Royale CLAN TAG #URR8PPP up vote 1 down vote favorite I decided to switch from Windows to Ubuntu 17.10, I meet it like 8 years ago and I didn't decided to switch until now (haha). Well, my actual device is an HP Probook 4540s with a Validity fingerprint sensor (VFS491). The fingerprint sensor worked fine on Windows but I can't get it to work in Ubuntu. The device is recognized as 138a:003d but is not detected as a fingerprint scanner by some apps like Fingerprint GUI. I want to use the fingerprint scanner to log in into my user account in Ubuntu but it doesn't supports fingerprints without special software and the drivers of the fingerprint scanner are available for Windows but not for any Linux distribution. I found something on GitHub (https://github.com/eekpie/libfprint) about the integration of the VFS491 in libfprint and I think it can help but I don't know what to do with it, so that's why I need the help of the community to do it since I am...
Read more