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.
I rebooted from putty on a windows machine over a local network with the "reboot" command. Now, upon going to the box I rebooted to see why it wouldn't accept another ssh session, it is in a perpetual (sp?) state of rebooting.
It gets to lilo, loads the kernel, then reboots over and over and over and over .........
????What the heck did I do????
I can boot the Slack cd and mount hda. I have no idea what to check for from there. I've been using Linux/Slack for about a year now and have been able to get myself out of most jambs but this one has me stumped.
It sounds like something else is going on... maybe check /etc/inittab for the default runlevel? I'd also take a look at the files in /var/log. Oh, and you might look through the init scripts in /etc/rc.d also.
Sorry I can't tell you exactly what to look for, but I hope this helps.
Look in lilo.conf for a lone "6" at the end of the kernel line or an "append=" line of the active/default stanza.
Explanation of #2
Both lilo & GRUB allow the passing of a an run level to init (see man init) from their menus (see man lilo.conf or http://www.gnu.org/software/grub/manual/grub.html). Usually we only see "1", "S", or "s" being passed, & that in the context of a failsafe or recovery mode -- all 3 indicate run level 1, single user mode.
Once I added 2 joke stanzas to a GRUB menu.lst: 1 w/ a "6", the other w/ a "0". I'm not sure which is funnier to foist on the unsuspecting.
In any case, the reboot looping you describe could be achieved this way.