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 using fedora core 5.
I can't use commands like iptables, lsmod and some other common commands.
Probably I didn't install a certain package but I don't know which.
they'll be there already, probably a path problem, which again is often caused by incorrect use of the su command. when you are logged in as a normal user, run "su -" to fully invoke the root users environment. alternatively, all these commands should live in /sbin/ so try /sbin/lsmod explicitly.
whilst the above is very possible, there is a reason these files are in /sbin/ it's because they are supposed to be accessed by superusers, not mere mortals.
By adding it to your path it may make you slightly complacent with using it (although you still have to use sudo or su), and things like iptables etc. can be a bitch if you give some silly rules by accident.
Logging in via su - is a good reminder that you should be careful with it.
Adding to /etc/profile will also append it to EVERy users path upon login, which you may not want.
It may seem paranoid but these mechanisms are in place for good reasons
whilst the above is very possible, there is a reason these files are in /sbin/ it's because they are supposed to be accessed by superusers, not mere mortals.
By adding it to your path it may make you slightly complacent with using it (although you still have to use sudo or su), and things like iptables etc. can be a bitch if you give some silly rules by accident.
Logging in via su - is a good reminder that you should be careful with it.
Adding to /etc/profile will also append it to EVERy users path upon login, which you may not want.
It may seem paranoid but these mechanisms are in place for good reasons
Good points...
I think I was assuming a root login, SU, or something.
I do find quite a few commands that I would like to access without using SU,SUDO, etc.
Another way would be to link certain /sbin commands into /bin
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.