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.
The times in lilo.conf are give in tenths of a second so a timeout of 20 is actually 2 seconds. I think that is just too fast for you to get into the menu. By the time you see it, lilo times out and tries to go straight into the default, "WindowsXP", which is not properly configured if I'm not mistaken. I think your windows entry should look like this:
instead of just:
so just add the table=/dev/sda line per the above.
Make the above changes to lilo.conf and then open a console, su to root and run:
# lilo -v
to write the changes to the mbr. Reboot and see if your menu entries work.
I use Konqueror to view the partitions. For some reason sda4 isn't mounted and I can't mount it because it's an extended partition. So I did some reading and ppl say not to mount the extended partitions but to mount the logical ones. So now I take a look at sda5, the / Fedora partition. For some reason the /boot dir in sda5 is empty. Was this because when LILO overwrote the MBR it deleted grub along with all the initrd and images? So how would I boot to Fedora? Well, the lilo.conf above gives me errors saying
Boot other: /dev/sda5, loader CHAIN
Fatal: First sector of /dev/sda5 doesn't have a valid boot signature
I also put the image and initrd from another computer with the same versions, but it doesn't work. I noticed that when I use other=/dev/sda4 for the Fedora option it says
Boot other: /dev/sda4, on /dev/sda, loader CHAIN
Boot image: /boot/vmlinuz-22.214.171.124-27
Fatal: open /boot/vmlinuz-126.96.36.199-27: No such file or directory
So it seems I need to add the image and initrd to this /boot dir in sda4, but since sda4 is an extended partition, I can't mount it. What do I do?
Thanks in advance.
I took out reset and change-rules. What do they do exactly? I checked out examples online and none had them so that's why I took them out. Also, the first line was blank, is there a reason for the first line being blank and starting the boot=/dev/sda on the 2nd line?
This looks like a real mess. You are mixing up chain loading concepts with standard lilo configuration methods. Basically, what you first have to determine is the path to the fedora vmlinuz and initrd.img as seen from Backtrack. To properly state that path, you need to have an entry in the Backtrack /etc/fstab for the boot partition of fedora which you indicate is sda2. Just to illustrate, let's assume that sda2 is formatted ext3 and Backtrack is to be configured to mount sda2 on /mnt/sda2. Then the fstab entry for sda2 in Backtrack would look like something like this:
/dev/sda2 /mnt/sda2 ext3 defaults 1 2
Your path to the fedora vmlinuz and initrd.img from Backtrack's point of view would be through that mount point, /mnt/sda2/boot/vmlinuz-188.8.131.52-27 and /mnt/sda2/boot/initrd-184.108.40.206-27.fc8.img.
Given this data, your lilo.conf entry for fedora would be:
After making these edits on lilo.conf and before running lilo -v to write them to the mbr, you have to mount sda2 or lilo -v will give an error as it won't be able to find fedora's vmlinuz or initrd.img if sda2 is not mounted.
Last edited by kilgoretrout; 06-24-2008 at 02:31 AM.