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.
never use x as root its very unsecure !!!
you can also do a liloconf and there type in a telinit 4 or edit the liloconf file and add appen="telinit 4"
and with xwmconfig you can change the default windowmanager to kde
You may also have to edit the /etc/rc.d/rc.4 file. Slack is configured to try GDM (gnome display manager) before KDM (KDE display mangaer) when in runlevel 4. If you have Gnome installed, you'll need to switch the GDM & KDM paragraphs in the file.
aaa - THANK YOU! I've been loooking for that for a while! I changed some login options in KDE, and they didn't apply, so I'm guessing that's what it is? (the option was the autologin, since I'm the only one using this computer)...
In the settings for KDM (there is a link in the special settings menu, along w/ kernel configuration & lilo configuration. In any case it should be in the kde control center), it has an option for this. I think it's in one of the last tabs.
If I'm understanding your question correctly, it sounds like what you want to be able to do is to power up the laptop, have root get automatically logged in, and then have KDE automatically start. I don't think it is possible to avoid the logging in step, but even if it is, I would urge you abandon this approach. Automatic logins are a horrible idea, and they're an order of magnitude more horrible if you are logging in as root. (As an analogy, what it sounds like you're trying to do would be similar to permitting somebody to use your ATM card without having to first input the PIN. Yipes!!)
I have a hard time imagining any scenario where somebody would consider the "logging in" step to be an unnecessary burden. Could it be that other people need to use that same machine, and you don't want to give them your ID/PW? If so, you can solve this issue by running the 'adduser' command and set them up with their very own ID/PW. I'll admit that maybe I just don't understand your true intent with this question, but as the other posters have indicated, logging in as root should only be done in rare, specific situations, and not done as the typical, standard, default behavior. -- J.W.
Originally posted by grassapa
if i change the runlevel to 4, it still prompts me for
a username and password, is there a way to have
it automatically log into root or a normal user?
ps i know i shouldnt use x as root, but this
is an exceptional case.
A mobile machine with a password-less root login?
That is, indeed, exceptional :} Exceptionally stupid,
one might add. I'd like to hear why you believe you
NEED to run as root, because I'm fairly certain that
there is a safe way to achieve what you need...
However, if you use KDE (and kdm as login-manager)
it should be a piece of cake to actually accomplish what
In Kcontrol, just go to the login manager, there
to the convenience tab, and 'eh voila'
ok, the reason i want to do this is because i want to set up linux for someone and he doesnt know jack about computers. so i want it to start up right to the desktop. but you guys are right about root, i should log him on as a normal user, but since he doesnt know jack about computers, he might never know how to log in as root if he wants to do something more complicated. and im not ever gonna talk to him.
now that thats cleared, let me ask
why is it so dangerous to be root? i know you can mess up your computer but you, or at least I, wouldnt do anything that you think it can be damaging to your computer. Every kind of config i make, i would consult it first on the net, and then do it. the reason i like to work as root always is that i can do everything fast. create directories, config preferences, etc. Since im a linux newbie, i dont know how to do many things as a normal user. Internet wise, its dangerous because as root, they can hack in to ur computer and do stuff, but after been living in windows for years, that doesnt scare me, after all, i have been pretty careful. Maybe, when i get better, i will realize why root is bad, but for now, i wanna know why and thats why i ask.
I have a little example for you, why one shouldn't work as root. It happend to me two or three days ago.
I was working as root, altough i should know better, because i started doing some file system stuff as root. After that tryed to enhance a little Shellscript of myself just to lern about the bash. Unfortunaly i made a really bad statment to the /bin/date file. The result was that the /bin/date file was overwritten and that i had to reinstall it from the rpm package.
If i had been working as a normal user, this wouldn't have happend. The /bin/date file is a file with owner root and group root, so only somebody (or any program!) who is stupid enough to work as root (like i am) can overwrite this file.
he might never know how to log in as root if he wants to do something more complicated.
Tell him that you normally should be a regular user for security, and certain things are not allowed so as to protect your computer, and if you really know what your doing, you can switch to root temporarily to do things. Tell him that it may be annoying not being able to do certain things, but these things were disabled for regular users for a reason.
Running as root is bad especially if you don't know jack about computers. Running X as root should not even be permitted, IMHO. If your acquaintance is really as computer-illiterate as you say, then maybe Linux is not the best operating system for him.
And certainly don't setup an auto-login for root. Anyone who does know a little about Linux might decide to play a prank on your friend (or on you, while you're away from your computer), open up a console and type 'rm -rf /', thus wiping out your hard drive in the blink of an eye. Not only is it like having no PIN on your ATM card, it's like leaving all of your money in small unmarked bills lying all over your front lawn, and assuming that nothing will happen to them.