[lfs-support] A question on Multiboot
Here's the situation. I've got two LFS systems, one on /dev/sda1 and the other on /dev/sdb1. They each have their kernels in the /boot directories on those drives. So I don't have a separate /boot partition. A little bit of an oversight on my part. I know I could back up things, erase partitions and start over with a separate /boot, but that's a lot of bother. So, what would be the proper grub configuration to fix it so that both systems can be booted? Right now, I have this # # # /boot/grub/grub.cfg on /dev/sda1 set default=0 set timeout=-1 insmod ext2 set root=(hd0,1) menuentry "GNU/Linux, Linux 4.7.2-newbean" { linux /boot/vmlinuz-4.7.2 root=/dev/sda1 ro } menuentry "GNU/Linux, Linux 4.2-l-bean" { linux /boot/vmlinuz-4.2-lfs-7.8 root=/dev/sdb1 ro } # # # That doesn't appear to work, however; I can only boot the 4.7.2 system. Does " vmlinuz-4.2-lfs-7.8 " need to be in the /boot partition of /dev/sda1 for this to work properly, since I have grub installed there? Thank you all for the help--and the patience. -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
Re: [lfs-support] A question on Multiboot
On Thu, September 15, 2016 13:08, Rob wrote: > # # # > /boot/grub/grub.cfg on /dev/sda1 > set default=0 > set timeout=-1 > insmod ext2 > set root=(hd0,1) > menuentry "GNU/Linux, Linux 4.7.2-newbean" { > linux /boot/vmlinuz-4.7.2 root=/dev/sda1 ro > } > menuentry "GNU/Linux, Linux 4.2-l-bean" { > linux /boot/vmlinuz-4.2-lfs-7.8 root=/dev/sdb1 ro > } You need to specify the Grub's root for each path to the kernel: menuentry "GNU/Linux, Linux 4.7.2-newbean" { linux (hd0,1)/boot/vmlinuz-4.7.2 root=/dev/sda1 ro } menuentry "GNU/Linux, Linux 4.2-l-bean" { linux (hd1,1)/boot/vmlinuz-4.2-lfs-7.8 root=/dev/sdb1 ro If recall, that is the way to do it and not use the variable set early for "set root=" > # # # > That doesn't appear to work, however; I can only boot the 4.7.2 system. > Does > " vmlinuz-4.2-lfs-7.8 " > need to be in the /boot partition of /dev/sda1 for this to work > properly, since I have grub installed there? > Thank you all for the help--and the patience. Sincerely, William Harrington -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
Re: [lfs-support] A question on Multiboot
William Harrington wrote: > You need to specify the Grub's root for each path to the kernel: > If recall, that is the way to do it and not use the variable set early for > "set root=" Thanks. That did the trick. -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
Re: [lfs-support] A question on Multiboot
On 09/15/2016 03:27 PM, William Harrington wrote: On Thu, September 15, 2016 13:08, Rob wrote: # # # /boot/grub/grub.cfg on /dev/sda1 set default=0 set timeout=-1 insmod ext2 set root=(hd0,1) menuentry "GNU/Linux, Linux 4.7.2-newbean" { linux /boot/vmlinuz-4.7.2 root=/dev/sda1 ro } menuentry "GNU/Linux, Linux 4.2-l-bean" { linux /boot/vmlinuz-4.2-lfs-7.8 root=/dev/sdb1 ro } You need to specify the Grub's root for each path to the kernel: menuentry "GNU/Linux, Linux 4.7.2-newbean" { linux (hd0,1)/boot/vmlinuz-4.7.2 root=/dev/sda1 ro } menuentry "GNU/Linux, Linux 4.2-l-bean" { linux (hd1,1)/boot/vmlinuz-4.2-lfs-7.8 root=/dev/sdb1 ro you can also just put set root on every entry: menuentry "GNU/Linux, Linux 4.7.2-newbean" { set root (hd0,1) linux /boot/vmlinuz-4.7.2 root=/dev/sda1 ro } menuentry "GNU/Linux, Linux 4.2-l-bean" { set root (hd1,1) linux /boot/vmlinuz-4.2-lfs-7.8 root=/dev/sdb1 ro I use it like this, didn't know about the possibility to prepend the kernel filename with the had. Cheers Tim If recall, that is the way to do it and not use the variable set early for "set root=" # # # That doesn't appear to work, however; I can only boot the 4.7.2 system. Does " vmlinuz-4.2-lfs-7.8 " need to be in the /boot partition of /dev/sda1 for this to work properly, since I have grub installed there? Thank you all for the help--and the patience. Sincerely, William Harrington -- decentral.ch - IT Stuff Tim Tassonis Dennlerstasse 36 8047 Zürich st...@decentral.ch +41 79 229 36 17 -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style