Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
yes, LILO and GRUB both support booting a Windows partition. The autoconfig for lilo (liloconfig) will set it up automatically. I don't use grub, but I'd be surprised if it didn't also automatically support Windows.
chainloading refers to loading of another bootloader. example, windows bootloader at the MBR, and lilo at the linux partition (just an example, not my config) On the windows bootloader, you choose linux, that loads lilo, which finally boots the kernel and initrd.img at the end.
that's chainloading... (correct me anyone if I'm wrong, but this seams pretty acurate)
and I think I found a solution to my problem anyway
If I understand you right, something like this, and Lilo will boot both. Install windows first on /hda1. Windows demands to be on a primary.
Then install Linux with Lilo installed to MBR. / could be on /dev/hda2, swap could be /hda3 ect. While you are configuring it let Lilo add an entry for windows too. When you boot Linux it will boot it, when you choose windows it will boot to ntloader.
You can have multiple distros of Linux on One drive partitioned up yes.
Use Lilo or grub to boot to each partition/image. I have used Lilo to boot windows, BSD, Linux.
I've used grub to boot Linux, windows, BSD. Part of Lilo goes on the partition and part on the MBR, if that's how you installed it. Lilo does not present a problem. Windows will if you install it 2nd or of you mess up ntloader.
fixboot and fixmbr sometimes are. worthless.
Originally posted by teckk You can have multiple distros of Linux on One drive partitioned up yes.
Use Lilo or grub to boot to each partition/image. I have used Lilo to boot windows, BSD, Linux.
I've used grub to boot Linux, windows, BSD. Part of Lilo goes on the partition and part on the MBR, if that's how you installed it. Lilo does not present a problem. Windows will if you install it 2nd or of you mess up ntloader.
fixboot and fixmbr sometimes are. worthless.
I am able to chainload windows (or ntloader). but can you chainload lilo or grub the same way you chainload ntloader?
Originally posted by mimithebrain I am able to chainload windows (or ntloader). but can you chainload lilo or grub the same way you chainload ntloader?
Yes, but it'll launch the menu for each - maintainance nightmare.
I prefer to have just one, and have one config file point to each kernel image - but everyone has their own preference on how this should be done.
IMHO grub handles this better - updates to the config are independent of the need to continually run the /sbin/lilo, and/or continually copy the boot sector record back to the Windows boot partition (if using ntldr as the initial loader).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.