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!
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.
I am fairly new to Linux, but have had a bit of experience in Debian Linux. I am now trying out the new Fedora 7 and having a few problems. Normally when I want to run a command such as
Code:
modprobe
I can just run it by typing
Code:
modprobe
as root and it works. However, in Fedora 7, I am having to type
Code:
/sbin/modprobe
in order for it to work. This is also true for any common commands. I was wondering if there was a way that I can change this so that I can just type the command like normal.
You need to be root for the command to work anyway. You could add /sbin/ to your path, but it may be better to leave it as it is and run the command like "sudo /sbin/modprobe ...".
Normal user commands aren't in /sbin. There are some user commands in /usr/bin. Make sure that that is in your path.
Thanks. I found out that if I log in as root from the login screen everything works as it should, but if I log on as my username and then open terminal and login to root using su then it doesnt work, so I guess I'll just log in as root when I need to perform those commands.
Thanks. I found out that if I log in as root from the login screen everything works as it should, but if I log on as my username and then open terminal and login to root using su then it doesnt work, so I guess I'll just log in as root when I need to perform those commands.
but I was having the same problem, but as long as I login as root from the login screen, then it works correctly. Not sure why, but I can live with it. Thanks anyways though!
No, they aren't the same. "su -" starts an interactive shell, so root's environmen, so root's ~/.profile script is run, setting up root's PATH variable. Simply using "su", you are running as root, but in your own environment.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.