DebianThis forum is for the discussion of Debian 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.
After installing all of the packages needed to compile kernel 2.6.8, and after successful installation of the new kernel, and after successfully booting the new kernel, I am unable to login using my username.
I can login as root with no problem. I have a single user system, but I login as root only when necessary.
All of the files in my /home/user directory are intact. The information in passwd is unchanged. I just can't login as user.
Using adduser I added a new user and password. Same thing.
I have upgraded my kernel several times and never had any problem.
At the login prompt I type in my username and get a message "System bootup in progress-please wait." And then, "incorrect login." The request for password never appears. I type in root and get the same System bootup...message, but I also get a "Password:" prompt.
Out of curiosity...did you do this recompile to get ATI drivers working? What other adjustments were made? I have seen this problem before, and both times were after installs of video drivers or updates to desktop environments. In both cases the installers had changed the permissions on crucial directories, and the user did not have access to them anymore.
When logged in as root, can you su into another user?
Can you log the user in into a different desktop environment?
As root, have you checked the user's group memberships and made sure they were not changed somehow? You could also check the groups themselves and make sure they were not altered.
This may be the wrong track to follow, but it is all I can think of at the moment. By the way, have you tried booting into your old kernel?
seems as if the script /etc/init.d/rmnologin is never started,
maybe you removed /etc/rc?.d/S99rmnologin or set default runlevel to single user (1) instead of 3 (mutliuser, network, console) or 5 (multiuser, network, X)
when the file /etc/nologin exists, its message is shown when a normal user tries to log in and the login is cancelled. only superuser can login while this file exists... (try deleting it manually for a test, but this will not fix your problem, the file is created by /etc/init.d/bootmisc.sh at bootup and deleted by /etc/init.d/rmnologin as last "boot job"
Originally posted by EliotK Not as long as you know what your doing, what can happen?
*EDIT* Yeah if your doing chat stuff on irc etc its better not to use root.
Sure, if you know what you're doing every time, then you are protected from yourself...but what about others? What about your system? It's supposed to be pretty dangerous to run X as root. Physical security is something you need too, what happens if you leave for a second and someone decides to mess with your computer? To protect yourself from your system like that, it'd be pretty tough; you'd need to read all the source code of every program you have on your computer and verify it's not gonna do anything you don't want it to. Then you'd need to read the source for each and every new program you get. That's pretty difficult if you're using a binary distribution. Plus, being connected to the internet while logged in as root for any more than a few seconds just seems like a bad idea. I'm no expert on the subject, so I can't go into detail, I just don't do it. To me, it's worth it to use "su".
Ok i get your point, but what are the chances? Ive always logged in as root for my 2 years of using linux, no asshole has ever tried to hack me or break into my house and use my comp while im taking a leak.
To answer your first question: a lot of people, me included.
For the second: I love Slackware, but haven't tried anything else...except I tried RH at first, but wasn't to happy with that. It's pretty easy to install and doesn't get in your way or do anything you don't want it to. Some people dislike its package management system, but I love it. It's nice and simple, nothing extra like dependency checking. If you want something that'll download software for you like apt-get, Swaret and Slapt-get are the most popular I believe. Also has nice little tools that make it easier to create your own. Plus, Slack has a simple init script structure, and I love that as well. Basically, Slack is simple and doesn't give you anything extra, and since it's Linux, highly configurable.