Quote:
|
Originally Posted by jiml8 NO!!
Never EVER do that!
You should NEVER have ANY directory for which you have write privileges in your path. To do so is to create a massive security hole in your system.
If you do so, you make it possible in principle for a bad guy to trick you into executing his bad program which you have inadvertantly written to a directory that is in your path.
If you want to execute a program in the current directory just invoke it with the ./ syntax. This is simple enough and prevents any possibility of a problem.
OP needs to download a compiled gcc. I think he is downloading source; lacking a c compiler, he can't compile a c compiler. I don't know where that will be found for linspire. |
With due respect, and not to hijack the thread, that is just ridiculous.
It is true that "." should be the LAST entry in PATH, for this reason, so that you don't execute a suspect ./cat instead of /usr/bin/cat, for example.
I've been working as a professional software engineer in Unix, for many companies and the federal government, since 1987. PATH has ALWAYS included the current directory. Not to do so will hamstring you as a user and developer.