Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then 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.
it really shouldn't matter at all. although i'd suggest using redhat or mandrake for fiddling with lilo, as i'd not be suprised if Lindows makes it far too obscure to do, but i don't know if it does or not. but the order should be pretty irrelevant, as it's all linux.
For easy setup you would install the distro you want to manage Lilo from last. That way it should detect your other Linux installs. Make boot disks for all.
Tinkster has a good suggestion about installing Lilo to the "/" (root) partition of the other distros. It saves some headache.
Nah, you can chroot into the / directory of the partition that lilo is to be ran from. Then, with full path, run lilo to make the changes. You don't HAVE to have it on a seperate /boot partition I don't
Originally posted by MasterC Nah, you can chroot into the / directory of the partition that lilo is to be ran from. Then, with full path, run lilo to make the changes. You don't HAVE to have it on a separate /boot partition ;) I don't
Heh ... to be able to add several kernels to lilo's
menu they need to be visible when lilo is run?
How do you chroot to two different partitions
at a time? ;)
chroot assures that lilo.conf is at the expected place, /etc
for the other vmlinux'es, you must mount the partition which contains them - preferably on /mnt/hd* so no matter what you boot, most of images will be in the correct place as indicated in lilo.conf
This does cause a dilemma - your question made me realize that I always have a "primary" partition from which I run lilo,so that the other bootables are always in a mounted partition.