On 2008/02/15 16:08 (GMT+0100) M9. apparently typed:
Berthold Gunreben schreef:
| I'd propose a different layout. Just create an extra partition for a | primary bootloader with something like 100MB. Boot that bootloader | from MBR and enter several chainloaders into menu.list that boot the | respective systems root partitions.
| Any system should have its own bootloader installed into the root | partition. For Win, it is just a chainloader anyways.
This looks as a very good solution to me also... As i am suffering from the everlasting problem, that grub entries dissappear, every once and a while....
| This procedure has the advantage, that you still can update the kernel | of each respective linux version without touching the primary grub | bootloader.
| ------------ | |primary | --------- | |bootloader|----------|Windows| | ----------- | --------- | | | | ------------ | |----|Bootloader| | | |X0 | | | ------------ | | | | ------------ | |----|Bootloader| | | |X1 | | | ------------ | | | | ------------ | |----|Bootloader| | | |ubuntu | | | ------------ | ......
| You would have to go through two different bootloaders at boot time, | but this is much easier than updating the kernel for different | distributions in a single partition (especially if those may use | different device names like sda and hda for the same disks).
Two bootloaders would not be a problem for me, but what when one installs a new os? It just starts booting the DVD or CD, and afterwards you create another entry in that 'masterbootloader?
Why wait? Use an existing installation to create and format the target partition, update the master boot loader with a chainloader entry to the new target, then do the installation.
Now i have a seperate /boot, about 153MB, carrying all kernels and stuff... But than, if i understand your suggestion correctly, the /boot, stays in / of every seperate OS. While this allready present partition could be used to host a 'Master' bootloader?
Sure. On a new system, install normally, except create a separate partition for /boot. Once installation is complete, edit /etc/fstab so that the original /boot partition is mounted somewhere else, or not mounted at all. Afterwards, reinstall first grub to the root partition's /boot directory, then reinstall kernel or copy old /boot partition kernel/initrd contents to new /boot. From then on, the only changes to the original /boot are changes you make manually - no changes from installers or kernel rpms - and no way for your Grub boot manager to get screwed up except by you doing it yourself. The net result is little different from installing some other boot manager on its own partition. For protection against having a windoz reinstallation mess up your boot loader, make the original /boot a primary, set it active, and install grub on it and not on the MBR. Grub will continue to work without any fancy reinstallation just by resetting its partition active after doz has done its dirty work, something you can do with any number of simple tools, including doz's FDISK. Only 2 bits in the MBR sector need changing to switch active partitions from doz's to grub's. See also: http://en.opensuse.org/Bugs/grub -- "For God so loved the world that he gave his one and only Son, that whoever believes in him shall not perish but have eternal life." John 3:16 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://mrmazda.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org