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!
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
This is because Lilo did not recognize and update itself for Fedora. It is a good option to use Grub. Its powerful. You can do it either way.
One is boot with Fedora media into rescue mode and then from the shell give the command:
grub-install /dev/hdc
Else there is another way of doing it. Boot into Slackware. And edit the lilo.conf file to add the fedora entry. I do not use Lilo so I am not sure how to do that.
The Slackware installation did recognize the partition as another install. It's just that the user needs to identify that install. You need to be aware of your system layout so as to enter the proper assignments for your installations.
You can enter the Slackware install then as root you can edit '/etc/lilo.conf' to include the proper entries by including the stanza for your other installs.
You would then run the 'lilo' command as root to update your loader.
If you post your '/etc/lilo.conf' file then we could assist. You could also do a search here on LQ as this subject has been covered many times.
Currently my problems are:
1) the grub loader did not load when i on my cpu. It boots straight into Fedora.
2) How to add the slackware into the grub loader?
Distribution: Mandriva 2009 X86_64 suse 11.3 X86_64 Centos X86_64 Debian X86_64 Linux MInt 86_64 OS X
Posts: 2,369
Rep:
AS root or su on the command line give the command ls - /dev/disk/by-uuid
It gives you all the uuid of you're partitions than mount the partition of slackware to find out the complete name slackware vmlinuz and initrd
Once you find it nano /boot/grub/menu.lst nano or pico or kwrite
title slackware
root (hd0,?) is partition ware slackware is minus 1
kernel and so on
initrd and so on
Any idea what have i done wrong even when i put in the slackware partition,it stills load the fedora?
I have also check from my laptop that when it boots slackware from LILO, it go to the /boot/vmlinuz to boot.
This is the LILO file where it boots the slackware:
Code:
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/sda3
label = Linux
read-only
# Linux bootable partition config ends
Thanks for the help in advance and thanks for reading my problem.
Last edited by vitalstrike82; 06-21-2009 at 10:36 AM.
When i install the Fedora, it prompts me if whether i want to install grub in /dev/sda
i guess /dev/sda is the MBR to boot the OS. Nevertheless, i install it into /dev/sda
While installing Slackware, it did prompt if i want to install lilo in my machine.
I choose not to set up LILO and skip the whole process of installing LILO.
Does that results in not able to boot slackware even when i select to boot from grub with the setting i have added into the grub conf file for slackware?
As long as you enter the proper configuration data in your stanza for your bootloader then you should be able start any installed system.
You can still setup lilo on the superblock for Slackware if you are chain loading then configure with your initial boot loader to boot that if you desire this method.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.