FedoraThis forum is for the discussion of the Fedora Project.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
If so you need to make sure the permissions (and ownership/group) are correct for the user that is attempting to run the command.
e.g. If a file is to be executed by only root then it should have root as the owner and have the execute bit set for owner.
chown root <file>
chmod 700 <file> (if a script)
-OR-
chmod 500 <file> (if a binary)
You can see current permissions, ownership and group with the ls command:
ls -l <file>
You can get more details with the man command for each of the above commands:
is so late at night here... that I misspelled that word...
tried it on root and didn't run...
is a patch file and I allowed it to be executed under my user name and tried it under
root and it didn't run... But I double click the file... some files under the right permission will run like that...this one didn't and that's why I need to know how to run it on the terminal....
Expanding on that - the "./" says "in this directory". This way you are sure the command can be found if the directory where it is isn't in your PATH variable.
You can see what's in that variable by typing:
echo $PATH
each directory will be separated by a colon.
If the file is named "patch" and you are in the directory where the file "patch" is then "./patch" should work so long as it is executable.
Last edited by MensaWater; 03-11-2007 at 03:42 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.