08-28-2016, 02:13 PM
"No, the changes made in my post above will not affect ability to boot other added distros as long as LL remains in charge of booting. However, if another distro's grub got installed to the MBR (replacing LL's) then same problem would occur in that distro's grub and the modifications above would have to be duplicated there."
"In addition, certain custom modifications to LL's grub (by the development team) will cause an error message when another distro's grub tries to boot LL."
"Therefore, in all multi-boot setups involving LL, leaving LL in charge of booting is the best way to go -- regardless of the particular situation in this thread. Basically, a person should just direct any other distro's grub installation to its own root partition instead of the MBR of the hard drive."
Thank you for that clarification. Most new users (windows converts, especially dual booters) need to know these things. Modifications are wonderful, and your solution works here, but not without possible complications down the road. It is worth noting that it's possible that shift key binding in this way could effect the use of Windows rescue media depending on the boot device ordering. Probably best to keep cd/dvd as the first boot device if possible. Shift is often linked to function keys on laptops, so again for pre-boot situations like widows rescue media, or live CD's the effect could be critical, if grub is in control when Windows opts to default to the media channel for rescue media. Some boxes with faulty OEM firmware actually run Windows on the media channel by default, locking device boot order to HDD first, and in such cases especially with laptop keyboards rescue media might not work at all if grub is in control with shift key binding when Windows boot fails, probably simply bringing up the grub menu again. Some laptops do not offer a pause key for boot device selection, some not even the option to order boot devices. Finally if the shift key is bound in grub, I wonder if edit character functions in the grub menu screen itself would work properly, or would it keep reproducing a new grub menu screen every time you shifted for character selection?
TC
"In addition, certain custom modifications to LL's grub (by the development team) will cause an error message when another distro's grub tries to boot LL."
"Therefore, in all multi-boot setups involving LL, leaving LL in charge of booting is the best way to go -- regardless of the particular situation in this thread. Basically, a person should just direct any other distro's grub installation to its own root partition instead of the MBR of the hard drive."
Thank you for that clarification. Most new users (windows converts, especially dual booters) need to know these things. Modifications are wonderful, and your solution works here, but not without possible complications down the road. It is worth noting that it's possible that shift key binding in this way could effect the use of Windows rescue media depending on the boot device ordering. Probably best to keep cd/dvd as the first boot device if possible. Shift is often linked to function keys on laptops, so again for pre-boot situations like widows rescue media, or live CD's the effect could be critical, if grub is in control when Windows opts to default to the media channel for rescue media. Some boxes with faulty OEM firmware actually run Windows on the media channel by default, locking device boot order to HDD first, and in such cases especially with laptop keyboards rescue media might not work at all if grub is in control with shift key binding when Windows boot fails, probably simply bringing up the grub menu again. Some laptops do not offer a pause key for boot device selection, some not even the option to order boot devices. Finally if the shift key is bound in grub, I wonder if edit character functions in the grub menu screen itself would work properly, or would it keep reproducing a new grub menu screen every time you shifted for character selection?
TC
All opinions expressed and all advice given by Trinidad Cruz on this forum are his responsibility alone and do not necessarily reflect the views or methods of the developers of Linux Lite. He is a citizen of the United States where it is acceptable to occasionally be uninformed and inept as long as you pay your taxes.