SlackwareThis Forum is for the discussion of Slackware Linux.
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.
It's generally a very bad idea to login as root for all of the time. I can only imagine the catastrophe awaiting someone who wants their computer to auto-login the super account. My recommendation, at most auto-login as your user account. Personally, I wouldn't even do that. You never know if one of your buddies/family members is gonna come over and use your computer, or if you yourself are logged in as root; then it gets really scary. You could inadvertently wipe parts of your system change all settings etc.
So, stay away from root if at all possible, and stick to a friendly user account for yourself. Only use the power when the power is needed, not any other times. Will make your system live longer.
Additional arguments may be provided after the username, in which case they are
supplied to the user's login shell. In particular, an argument of -c will cause the
next argument to be treated as a command by most command interpreters. The command
will be executed by the shell specified in /etc/passwd for the target user.
The KDM session manager can do that. On SuSE Linux you would go the the 'Edit Groups and Users' setup dialog to make the change. I don't know what you have for slackware. You can use KDM to login to the window manager of your choice. However, the common way to set it up is to use the kcontrol program. But if KDE isn't installed, I don't know if you can use it, or exactly what changes it would make, such as changing the /etc/inittab file and making changes to the /etc/pam.d/ configuration files.
Also, using autologin is potentially dangerous and shouldn't be used if you access the Internet, or if you have a user on the local network that you don't totally trust. For example, if the changes add an option to KDM or mingetty this may be readable in /proc/<pid>/cmdline.
You should only use it if you want to run a kiosk.
Originally posted by win32sux oh, okay... i did look at the man page before asking, i just missed that part... my brain was looking for a bold -c on the left... hehe...
BTW, what about putting a "-" before the username??
i'm curious cuz it says:
sounds like something that might be useful... what do you think??
you may or may not have to do that. if it works, it probably doesn't matter too much. you might want to do it just to be safe
Originally posted by jschiwal The KDM session manager can do that. On SuSE Linux you would go the the 'Edit Groups and Users' setup dialog to make the change. I don't know what you have for slackware. You can use KDM to login to the window manager of your choice. However, the common way to set it up is to use the kcontrol program. But if KDE isn't installed, I don't know if you can use it, or exactly what changes it would make, such as changing the /etc/inittab file and making changes to the /etc/pam.d/ configuration files.
ooh.. firstly.. you need far more kde components than would be worth it, and, what? PAM?.. I know naught of what you speak. (not in slackware)