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.
If the first word on a command line, which is almost always a command, does not contain any "/" characters, your shell tries to find the command you're trying to run.
To do this (unless the command is a built-in, an alias or a defined function), the shell searches the directories that are contained in your PATH variable, which usually has a list of one or more directory pathnames seperated by ":".
You can view your current PATH by entering:
echo $PATH
It will include /bin and or /usr/bin, but not /sbin.
If you enter:
PATH=$PATH:/sbin
you can then run fdisk -l without having to qualify its location.
To make this change to the PATH variable permanent, edit the .profile file in your home directory and add that same line of code (PATH=$PATH:/sbin) somewhere in the file, then the next time you log in, you'll be able to run any of the commands in /sbin without having to tell the shell where to find them.
I'm not sure, though, why the output is blank. I'll boot up my Linux laptop and check it out.
One other way to get fdisk to give you output without using sudo or becoming root (with su):
Become root, then enter:
chmod u+s /sbin/fdisk
This enables the Set User Id bit on the executable, so anyone can run fdisk and the process will have an effective user id of 0, indicating that root is running it.
A word of caution, though, that will allow anyone to use fdisk, albeit they'll have to run /sbin/fdisk, but it can do far more than just produce reports. It can reformat a disk...
Best regards,
Walt Uotinen
Last edited by waltuotinen; 10-01-2009 at 05:22 PM.
Don't do this if any other person might ever have access to your computer. Use sudo. log into the root user. dont give such huge system access to all users if you have any expectation of your computer surviving other people's use.
Easiest way, set up sudo. Configure it so you can use it and it will null your authentication after 30 seconds or so. Keep it secure
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.