i am getting command not found error when i am trying to perform commands in linux?
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Saying what commands would help. If it's something you've installed, it may have ended up somewhere off your path. If it's something meant for root it may be off your path or you may not have the right permissions. Check out the man pages for 'bash' regarding 'path' and for 'chmod', I guess, to get an idea of permissions. Either editing your path, changing perms, or moving the executable someplace appropriate should do it. Or, if it *is* something you need to be root for, 'su'.
Oh, just noticed that was post #1 - welcome to LQ.
I'd suspect you'd need /sbin or /usr/sbin on your path or need root permissions/paths. Try a 'which pvscan' to see where they are, assuming they're on the system at all. Then install them, add the path they're in to yours, 'su' to root - whichever's appropriate. I figure it's just an 'su'. If not, 'export PATH="$PATH:where-it-is"
Hm. That's strange. I have env in /usr/bin/env. I don't have much occasion to use env, but it still oughtta be there. I usually use 'set' to see everything or 'echo $VAR' to see a specific variable. This is assuming bash, actually. I'm not sure how other shells work. I guess I'd try the same principle - except I told you wrong - 'which' won't help you find something to put on your path if it's not on your path. Try 'whereis env' and then 'echo $PATH' - if the path 'whereis' shows isn't shown by 'echo' then it'd be a case of adding it, too. But that wouldn't explain how env got lost. I'm guessing there's a typo or something in one of your shell config files.