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.
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:
It will include /bin and or /usr/bin, but not /sbin.
If you enter:
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.
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