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.
Correct, su is a shell command, not a user name unless you did actually create a user called su. Correct also that in some cases a direct logon to root may be disabled.
Su is really a command to switch user. With no user name added most distro's default to su root. You can su bob or su sally or such. If your root has been renamed to fred then su fred would be admin/root.
We tend to suggest that you log on to your user and then use the command sudo. The password would be your users password.
Distribution: Fedora KDE, and Android 4.3 Cyanogenmod 10.2
Originally Posted by theKbStockpiler
When I Control>Alt> f1 and go to the console, I can only log in as su after I log in as my user name. Why is this?
Simply put, hitting the alt_F1 tells the system to start a whole new login, so before you can use "su" to sign in, you must log in as a user to begin with. Then you can log in using the "su" command. It happens like that because the system needs the user logged in in order for it to very the user credentials assigned to that user (as listed in the /etc/group file.) For a clear example, an administrator may have restricted a user to be able to not play games only or use the sudo command to make changes, say if it was a computer at a company to keep play time and systems security in check. If the user was not assigned to the adm, trusted, root, or wheel group, then using a virtual terminal login will not allow a user to use "su" at that point.
Oh, and as mentioned above, Ubuntu users must issue the command "sudo su" first before ever being allowed to login using "su". It's a double check for additional security to verify admin rights, essentially.
Last edited by youniqueg33k; 11-29-2013 at 05:48 PM.
Reason: additional info
Distribution: Fedora14,Scientific 6.1?, Mandriva 2010 ;GO MAGEIA!!!Next up Gentoo
Thanks for all the replies!
I actually never gave it that much thought and I totally forgot about the root user. I thought (su) stood for superuser and that was a users name. I'm centered on Mandriva's 10 logic and I think Scientific/Centos where as you can switch to root user and also be in X which is nice and never understood the sudo type of logic.There is a huge void in my linux understanding of the sudo thing. I have read many a turtorial on it and it seems like total BS. When I try to login as su it does display "incorrect login" because there is no user account of su of coarse.
The console is what you interface with when X is not running correct? Is the log in application its own or is it a command that is part of a shell, a shell being a occurace of Bash?
Last edited by theKbStockpiler; 11-29-2013 at 09:04 PM.
The console is a hardware device on your system (usually hooked up to the keyboard and monitor, but there are other types such as serial consoles -- back in the olden days VT-100 terminals were hard-wired into a minicomputer). Linux (and other *nix-OSes abstract its functionality so you can have multiple virtual terminals (usually there are 6 tty1-tty6 on a Linux box, but there can be more or less depending on the config). These virtual devices are configured to run /bin/login, which is what actually accepts a user name and password (or other credential like a smart card when thsoe are used for authentication). Most systems nowadays actually use PAM (pluggable authentication modules) to do the heavy lifting of authenticating a user. This is so admins can customize how users are authenticated in a consistent way accross multiple aplications (e.g. terminal logins, ssh, ftp, the su command itself, etc.).
Once a user log in to a text-based console, whatever shell is configured in /etc/passwd (or its moral equicalent, such as an LDAP directory) is executed. The bash shell is just one of several available on Linux and Unix systems, but it's probably the most widely used. Other popular ones are csh, tcsh, ksh, and zsh, all of which havbe slightly different command sets and features (bash, ksh, and zsh are all related back to the Bourne shell, while csh and tcsh use a rather different command set). If the user wishes to use a graphical desktop, they must start it by hand (usually by typing "startx" on a properly-configured system), Most desktop systems, though, are configured to start a graphical login manager at startup, which can also accept authentication credentials and start up a grtaphical desktop for the user.