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.
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.
I went on a Linux install rampage last night just for kicks installed Slackware, Knoppix, Mandrake, and Red Hat (all successfully bootable). Slackware is essentially my "master" linux in that all the other distros' boot information is stored in Slackware's /boot (in their respective folders). I just copied the /boot dir into slack from all the distros and added the necessary lilo entries.
Is there another way of accomplishing multi-boot? The reason I ask is what if my Slack partition gets corrupt? I could still recover from it, without losing all my other distros, but it would still be quite a bit of work.
Just curious to hear how other people have dealt with booting multiple linuxes (or is it linuxii hehe).
my way of doing things is to create a small partition just for booting/bootloader. that means when I have to re/install something, say like a windows-type os that usually destroys all other bootloaders, I can just set the desired partition active and do the stuff (so windows boots automatically, if we talk about this example) and then re-activate my actual boot partition. this is handy in other cases too...so if one distro-partition gets screwed up, it won't affect my bootloader
Did you create the boot partition manually or did you let a distro create it during its install? What is in your MBR? I understand what your saying, I'm just not sure how you went about accomplishing that.
Distros like Fedora/Red Hat like to make boot partitions. You can make a boot partition yourself easily.
I suggest you use Grub with the boot partition, it is more independent than lilo. You can configure grub to put everything (cfg file, itself) on the partition, so it is totally independent. With lilo, it will run on a boot partition even if the os that installed gets messed up, but reconfiguring it will be difficult.
Yes. You will also want to make sure the grub cfg file is there too (no /etc/grub.conf, you want it in /boot)
Edit: I don't think the boot flag matters, it is a DOS/Windows thing.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.