When you are a developer, you have to test your software with many distributions (Fedora17, Fedora18), Ubuntu, Mint14, Debian), for both 64 and 32bit systems. I have learned to not test with a Virtual machine.
With grub2, one of the distributions is the master. It;s grub.cfg has a menu for every distribution. That means that any kernel update in one distribution requires creating a new grub.cfg from the master distribution (typically from the distribution that was installed last.
I was thinking that we should have a grub3 master with the following properties.
It has only the grub.cfg information for itself, and a dynamically created appendix with the grub.cfgs from the other linux distributions.
When you boot any of the distributions, the grub.cfg process would scan the other disks for their latest versions. In effect, if Ubuntu updated the kernel and its grub.cfg, the boot process from the booted distribution would create the selection menu. In otherwords, If I happen to be working in Ubuntu, and I apply updates, when I next reboot, the master grub.cfg would detect this by reading the distributed boot information.
Adding or subtracting a distribution would not require changes to the master grub.cfg, and ... I believe the problem I am encountering as I listed in my previous posting would not pose a problem. This approach would allow me to plug in an external drive, and to be able to boot from it on a subsequent reboot
If I am full of wrong thinking, please let me know.
With grub2, one of the distributions is the master. It;s grub.cfg has a menu for every distribution. That means that any kernel update in one distribution requires creating a new grub.cfg from the master distribution (typically from the distribution that was installed last.
I was thinking that we should have a grub3 master with the following properties.
It has only the grub.cfg information for itself, and a dynamically created appendix with the grub.cfgs from the other linux distributions.
When you boot any of the distributions, the grub.cfg process would scan the other disks for their latest versions. In effect, if Ubuntu updated the kernel and its grub.cfg, the boot process from the booted distribution would create the selection menu. In otherwords, If I happen to be working in Ubuntu, and I apply updates, when I next reboot, the master grub.cfg would detect this by reading the distributed boot information.
Adding or subtracting a distribution would not require changes to the master grub.cfg, and ... I believe the problem I am encountering as I listed in my previous posting would not pose a problem. This approach would allow me to plug in an external drive, and to be able to boot from it on a subsequent reboot
If I am full of wrong thinking, please let me know.