Results 1 to 5 of 5
Enjoy an ad free experience by logging in. Not a member yet? Register.
uh-oh, I think something bad happened to my slack box...
AHH!! In a panicked rush I format and threw Debian on my box, I don't know what happened. Was this my fault for putting everything as root for the pkgtool question? If so why was I not able to log in as root? I was not running a server at all, I dunno what happened here.Registered Linux user #393103
Since you wiped Slack, you really can't tell what happened to your box. When something like this happens, I'd run a rootkit scan and check all logs for anything that looks odd. That's always the starting point.
Unfortunately, this isn't possible if you've wiped Slack."Time is an illusion. Lunchtime, doubly so."
~Douglas Adams, The Hitchhiker's Guide to the Galaxy
Yeah.. I was in a panicked rush and erased it. It really scared me when I couldn't log into root. I did have chkrootkit installed actually but what good would it have done if I could not get into my system? It kicked me out when I tried to login to my user and root. I think I did the right thing and formatted the moment I knew what was going on.Registered Linux user #393103
Disconnecting the net and resetting the root password in single mode would of been the best thing to do, then you can figure out what was wrong, why it was wrong, and how to fix it so it doesn't occur again.
If the machine still didn't allow you to login after you reset the password, the chances are high that it just wasn't allowing local root logins, I have root logins on the local machine disabled and always use su from a user account, if I do something that stops me logging in at all then I can just fire up install cd 1 and recover the system with the command line it provides
09-05-2005 #5Originally Posted by KrendoshazinLinux user #126863 - see http://linuxcounter.net/