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 have RedHat8 installed and coexisting with Wirus 98. After an Fdisk disaster I recovered all the partitions, but GRUB doesn't work anymore. I installed the XOSL bootloader to have a working system, but cannot access Linux, just Windoze.
I can see the correct Linux filesystem from a TestDisk program, so the data is still there -- I just can't boot to Linux. I need some of that data with the original configuration, (license manager links, etc.) so reinstalling RedHat is out of the question.
The XOSL manual says it can boot Linux, as long as there is LILO installed on the linux partition.
The question: How do I add LILO to an existing install without reinstalling the whole kit?
Note that there wasn't any LILO in the first place; I chose GRUB, but it is now dead. I have access to another linux system, and can create diskette images and the like, as long as the procedure is not to complex.
OK, let's assume I can write a correct lilo.conf (based on samples from a working system and some reading). But step 2 is still going to be a problem -- how the heck can I run /sbin/lilo on a system that won't boot to linux? I sure can't run the thing under Windbag :-)
I'm thinking more along the lines of 1. Getting the stuff ready somewhere else and copying it onto the linux partition (assuming I can get into the filesystem somehow, maybe from Knoppix) or 2. Booting the linux from a diskette image -- the problem is, how do I point the boot loader from the diskette to the right partition? I would be creating the diskette on another system, with different configuration.
Update: the kernel panic problem seems to occur because the dumb thing doesn't know where the linux partition is. I do know -- it's the second (primary) partition on the first hard disk -- but how do I translate this knowledge into a form comprehensible to the LILO?
Thanks! This Knoppix trick should work. I didn't know I could boot from Knoppix and then pretend I booted from the original RedHat. I'll have to try this tomorrow, though, as I don't have the Knoppix CD with me.
My plan now (thanks to the help I got)
1. Boot with Knoppix as you said
2. edit lilo.conf
3 run /sbin/lilo
and then it should work, right?
P.S. what do I specify in lilo.conf to make sure LILO installs on the linux partition, and not in the MBR or the first partition?
I typed linux root=/dev/hda2 rw at the diskette LILO prompt. The thing has kept trying to boot from hda3, which is the swap partition. It took me a while to figure out the proper syntax, though.
What the problem was:
As I said, I recovered the partitions after an fdisk misuse (to put it mildly -- actually what I did was remove the partitions on the wrong drive :-O).
It appears the partitions were in different order previously, so what is now hda2 used to be hda3 -- and the boot diskette couldn't figure it out.
Now on to the next step: configuring and running LILO.
P.S. But first I'll edit lilo.conf on the diskette, so that it points the right way. Shouldn't the darn thing be able to recognize which partition is the right one? There is only one disk, and only one ext3 partition on it. Oh well....
P.P.S. I still don't know how to make sure LILO installs on the linux partition only when it runs. I'll figure it out eventually.