Greetings, Lets say I have a bunch of partitions, one of which contains a working linux installation that uses grub to boot. "linux1"
Now I install another linux2 on another partition. In a friendly way, it generates a new menu.lst for grub that allows booting either the linux1 or linux2. All is rosy until... linux1 distro gets a kernel update, rewrites _its_ menu.lst in blissful ignorance of linux2. So linux1-updated-kernel doesn't appear on the menu after reboot because the menu is the one on *linux2* partition. It is necessary to copy the updates across by hand from linux1 to linux2 Now enter linux3, linux4... aagh. Does anyone have a cunning way around this sort of bootloader conflict? I'm thinking either having all the installations somehow maintain one master menu.lst or have a master grub menu that offers a choice of the menus of each installation. -- Eliot
