Why do we use ./filename to execute a file in linux?

Why not just enter it like other commands gcc, ls etc...

  • Wouldn't the first line be better written as "Why do we use ./command_name to execute a command in linux?" – user15760 Jul 26 '13 at 6:18

In Linux, UNIX and related operating systems, . denotes the current directory. Since you want to run a file in your current directory and that directory is not in your $PATH, you need the ./ bit to tell the shell where the executable is. So, ./foo means run the executable called foo that is in this directory.

You can use type or which to get the full path of any commands found in your $PATH.

  • 5
    It is very common to execute programs in the current directory. Why doesn't the shell search in there as well? It first searches in ., then in $PATH. – Michael Jul 9 '13 at 22:14
  • there are also aliases that can get in the way, not just $PATH . – user2485710 Oct 14 '14 at 21:35
  • 18
    @Michael security and sanity: If it searched in . first then it would be a security issue, you or someone else could replace ls for example (a simple virus/trojen: make a zip file with an executable named ls in it, as someone is searching through, they run this executable, that …) . If it searched in . last then you can spend a long time going crazy not knowing why your program is not working (e.g. you make a program called test, instead of running your program it runs the systems test program. Which produces no output). – ctrl-alt-delor Mar 14 '15 at 18:24
  • It also ensures that if the application or script appears multiple times in your path, that you are executing the version that you intend to run (the one right here in your "." directory). – Jim2B Jul 7 '15 at 18:43
  • You can execute export PATH="$PATH:." to execute command in current directory if not found elsewhere in PATH, you can add this in your .bashrc file – jcubic Apr 23 '17 at 10:01

The literal answer is as others have given: because the current directory isn't in your $PATH.

But why? In short, it's for security. If you're looking in someone else's home directory (or /tmp), and type just gcc or ls, you want to know you're running the real one, not a malicious version your prankster friend has written which erases all your files. Another example would be test or [, which might override those commands in shell scripts, if your shell doesn't have those as built-ins.

Having . as the last entry in your path is a bit safer, but there are other attacks which make use of that. An easy one is to exploit common typos, like sl or ls-l. Or, find a common command that happens to be not installed on this system — vim, for example, since sysadmins are of above-average likelyhood to type that.


If you mean, why do you need ./ at the start - that's because (unlike in Windows), the current directory isn't part of your path by default. If you run:

$ ls

your shell looks for ls in the directories in your PATH environment variable (echo $PATH to see it), and runs the first executable called ls that it finds. If you type:

$ a.out

the shell will do likewise - but it probably won't find an executable called a.out. You need to tell the shell where a.out is - it it's in the current directory (.) then the path is ./a.out.

If you're asking why it's called "a.out", that's just the default output file name for gcc. You can change it with the -o command line arg. For example:

$ gcc test.c -o test
$ ./test
  • Thanks.My doubt is why do you need ./ at the start.... I got the use of "." (to poit the current directory) but why "/" after that? – Renjith G Nov 30 '10 at 8:35
  • 8
    / is the path separator in Linux, so you use it to separate the directory (.) from the filename (a.out). Without it you have .a.out which is a valid filename in its own right. (Try touch .a.out; ls -lA to see this.) – Simon Whitaker Nov 30 '10 at 8:37
  • 5
    that is how you specify the path in Unix, <dir>/<file> so you are basically saying execute a file in the current directory, which is indicated by ./test – Rohan Monga Nov 30 '10 at 8:37
  • Red Hat Linux release 9 (Shrike) Kernel 2.4.20-8 on an i686 [renjithg@cvsserver renjithg]$ touch .a.out;ls -lA total 3 -rw-rw-r-- 1 renjithg renjithg 0 Nov 30 13:46 .a.out -rwxrwxr-x 1 renjithg renjithg 11669 Nov 30 13:46 a.out -rw-rw-r-- 1 renjithg renjithg 218 Aug 24 2009 aray.c [renjithg@cvsserver renjithg]$ – Renjith G Nov 30 '10 at 8:48
  • 3
    Red Hat Linux 9? Time to upgrade! – mattdm Feb 17 '11 at 1:53

You can try to add :. to your $PATH variable.

Try ALT+F2 and type: gksudo gedit /etc/environment if running Linux/GTK (this is what you have if using Ubuntu).

HOWEVER, I strongly advise you NOT to do that. It's bad bad bad and bad.

You know, that kind of things work like this since 1970. There is a reason why the current directory isn't included in the $PATH.

. is the current directory

.something would be a hidden file (Type "ALT+" to make them appear in Nautilus, or try "ls -la".

./someProgram.sh is what you type to RUN an executable someProgram.sh in the current directory.

.somethingElse would mean that you have a hidden executable in the current directory, which is a bad idea.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.