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.
After reinstalling W2K on my multi boot system, it wiped out lilo. So I tried to use the emergency boot disk to access Mandrake 8.2, but it produced an kernel panic error saying that init could not be found. and suggested passing init= to the kernel. Upon advice os some friends, I have tried a couple of suggestions, but none worked. MDK8.2 is install as the third drive with four partititions, which are / at hdg6, swap at hdg7, usr at hdg8, and home at hdg9. Outside of this, the file system structure is as dictated by MDK's own setup during the installation. If I understand the issue, it is that I must direct the system to where the lilo config file is located, but since it is impossible to navigate within the file system, I can only assume that it is located whereever it should be. Would someone be kind enough to give me the exact syntax to enter, in order to tell MDK where to look. I have been criticised for not giving enough detail when asking a question on another forum, but this is all that I know, if more is necessary, please tell me how to find out.
Hmm, unless this route does something different than using the emergency boot disk, then perhaps the point of my question wasn't clear. I need to deal with the kernel panel error, before I can restore the lilo. Maybe I have been mislead by previous conversations, so I will try your method as soon as I finish posting.
I took a look around in /etc and there is no linux.conf in that location. I did a "whereis" and it found nothing. I tried "which", and it doesn't seem to work in that console.
The error message when booting from the now existent lilo, is different than when I used the emergency disk, yet it seems to boil down to the same thing:
"VFS: Can't find ext3 file system on dev/IDE3 (34,7)"
"Mount: Error mounting ext3 flags kernel panic no init found. Try passing it= option to the kernel".
IDE3 is the one on which the harddrive connects to the ATA/RAID controller. But since the console can read the system files, apparently the error message is misleading.
The emergency boot disk error only said something like "Kernel panic, can't find init. Try passing init= option to the kernel. Nothing about the IDE 3.
I did locate Grub in...I think usr/sbin, but I guess this would do no good without linux.conf...yes? Since it appears that linux.conf doesn't exist, can it be reconstructed, or simply copied to the proper location, using a copy from someone else? Probably not,but I'm looking for any kind of an answer to save the installation.
I tried to install lilo.conf last night, but failed. Either the syntax that I tried is wrong, or ? If I did an upgrade installation of the system, without selecting any packages except lilo, would that leave all of my original installation, files and documents intact?
he he he, all the way down to your 2 mice (why 2?)
Thanks for the very detailed info. No, you should be fine pluggin in your install CD, upgrading, and ONLY installing LILO, configuring, and booting. I've done the same thing with Mandy back in my early days, I couldn't live without pico, so I'd plug in the install CD, choose "upgrade" and only choose pine to be installed, a lot of work for 1 package...
However, it did nothing to the rest of my setup, so it was exactly what I wanted.
Great! Then that is what I will do. I'm still not certain that will make it work, because I have been working with a couple of recovery programs, which have produced the file systems from Linux 8.2 as well as my deleted archive and the rest of the drives. I don't understand the programs too well yet, but it appears that more than lilo may be missing. If this upgrade doesn't work, then I will just try to salvage the system of what I need, and then reinstall it from scratch once more.
I know why this installation went bad on me, but I have installed 8.2 more times than I remember, because of various problems including kernel panics, corrupted sound system, etc. and I have yet to figure why these problems continue to reoccur. I sometimes think that it is my motherboard or the Highpoint ATA/Raid chip built on it.
Why two mice? At one time, it was because my first Explorer mouse went bad, and I bought the Logitech, rather than hassling with MS, but after conversing with some others, I went ahead and got an RMA to replace it with. Now however, it is out of necessity, because it seems as though Windows doesn't like the USB mouse connection, and Linux doesn't care for the PS/2, so rather than constantly switching, I keep one connected in each way.