Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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 was booting into my RedHat partition just now, after attempting to install the Atmel drivers. I got the message "<o> Kernel Panic: Attempted to kill init!" What does this mean? Please help! I have kernel 2.4.18-14, i586.
When I reboot, I am greeted with a message telling my to "run fcsk manually without options". Then, I am dumped to a shell, I login as root, and I see the prompt "Repair File System # 1" The number changes for every time I press enter.
Ok, this just got a little more complicated...
I tied what you said, fsck /dev/hdb1 (A is my XP drive). It ran through some checks, and rebooted. Now, it gives me yet another kernel panic, "Aiee Killing interrupt handler!". So, I tried the same thing again. after I hit <enter>, after typing fsck /dev/hdb1, it just sits there, flashing a cursor at me. What can I do now?
ok, problem, I tried to run the script, but it "has been removed from the kernel". Apparently, I have to re-download it from Kernel.org. But, I'll do that later and post the results here, sorry, and thanks.
Right, I found it there, BUT, when I tried to run it, it said that I hadn't specified enough information, and it showed me a list of - orptions ie. -V, which was the one that it recommend I use, so I did and the system hung up. What sould I try, just try it again?
are you actually getting into the linux box? or is it just sitting there on boot?
an alternate/easier way around, is to recompile your kernel plus you get the benefits of new drivers etc, but if you stil like to solve this problem you could install both kernels and keep working on the other problem.
try it with something like
/usr/bin/ksymoops -m /boot/System.map
i'll keep thinking for you
(but as i say if you really need your box up install a new kernel)