Hm. I think you have your boot partition because you have another linux, maybe as stable version, ant want to try out gutsy on a separate partition, but with the sme /boot partition.
On the first glance this seems to be a good idea, because you can select each of your operating systems within one menu. But IHMO that is no good idea, because: 1. In debian/ubuntu there is an update-grub script which creates the automatic boot items. this script only chooses the kernels of it's own partition/system, all othere options you have to write per hand. So in case you have your gutsy tribe 4 installed, and - as you wish - the installer adds your new gutsy kernel to the single /boot grub-menu, it has only the possibility to start it directly, like: e.g. title Ubuntu Gutsy Tribe 4 root (hd0,0) kernel /boot/vmlinuz-blahblah root=/dev/sda3 initrd /boot/blahblah And that as manual add, which means IT WILL NOT BE UPDATED IF YOU INSTALL A KERNEL UPDATE! which is bad. so you maybe see, "fixing" this would be an issue not only to this installer, but also to grub/debian scripts etc. I think the much, much better way to do this is: keeping your boot partition, and install the gutsy GRUB into the partition, not the MBR. Then you can manually add a "Testing" boot menu item which chainloads the partition bootloader. Each system keeps separated. You don't have to make another menu in gutsy, just don't prompt. Hope that helps Cheers, Chris -- /boot partition doesn't need to be formatted ( gutsy tribe 4 ) https://bugs.launchpad.net/bugs/132840 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
