Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.

Notices

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.

Hi all,
I am using Linux centos in vmware, after rebooting Linux machine suddenly i got an error message "Kernal Panic error" cant able to boot...How to solve this..
Kindly help me in solving this issue..

First of all, "what is a kernel panic?" It is a situation where the kernel finds that it is impossible to continue; where it has no choice but to grind to a screeching halt. The panic is a consequence of whatever fatal condition immediately preceded it.

The message probably contains the message, "(not syncing)," which is very good: it means that a disk-write to the file system was not in-progress at the instant that the kernel died. (If it was "syncing," you probably now have a corrupted file system ... at best.)

Probably the most common point where you will see a panic is at system boot. Several things have to happen in very quick succession at this point: mounting the root file system, finding the init process and launching it, and so on. If any of these steps don't succeed, the system has no alternative but to halt.

Another slightly-less obvious situation is described as "tried to kill init," when a better description probably would be: "init died." This very-special process ("process #1") controls virtually everything and, as such, it is literally not allowed to die. Yet it is "an ordinary executable," dependent on such things as glibc and so-forth as well as the occasional direct or indirect bug. If this process dies, the system will immediately panic.

So ... your immediate question really can't be answered. By saying, "I have a kernel panic," you're only saying that your car is stuck by the side of the road. It doesn't say why it got there. HTH ...