Haven't really gotten an answer to this despite a lot of searching/reading, so if it's somewhere here, sorry, please give me a link.
While using grub-legacy, I used chainloading for windows AND secondary linux systems. IOW, grub was installed on the mbr and the secondary linux partitions. That way, I never had to reboot to the primary linux system to update-grub, it happened automagically when the secondary system kernel was upgraded. This worked well and was essentially ZERO maintenance.
When grub-pc took over, I used the same method, and it worked too, with one exception -- grub-pc does not like to be installed to non-mbr partitions. It complains about unreliability etc. It will install if given the --force option, and I did that with no noticeable problem. But this bothers me. Will this method cause problems? Are others doing it this way? Is there a good reason not to do this?
thx,
feffer
Grub2 >grub2 chainloading
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Grub2 >grub2 chainloading
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Re: Grub2 >grub2 chainloading
feffer wrote: When grub-pc took over, I used the same method, and it worked too, with one exception -- grub-pc does not like to be installed to non-mbr partitions. It complains about unreliability etc. It will install if given the --force option, and I did that with no noticeable problem. But this bothers me. Will this method cause problems? Are others doing it this way? Is there a good reason not to do this?
thx,
feffer
The complain on 'unreliable', it is a BAD idea, etc always appeared in any grub2 update, especially those with kernel changes, such as testing repos, sid repos, I read this many times.
I used grub legacy as Master Boot Loader, which control MBR of each hard drive, including USB flash and USB external drive.
Each time I install new OS to a partition, I always choose its default boot loader ( whether it is LILO, Grub 0.97, Grub 1.97, grub 1.98, grub 1.99beta?) to install onto its root partition, therefore they do not mess with MBR.
I did that so that the partition is chainloadable.
I ignore these 'complaints' and so far have no trouble.