-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Berthold Gunreben schreef: | On Fri, 15 Feb 2008, M9. wrote: | |> 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? |> |> 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? | | I don't know an automatic method to set this up. What I did was just | the same as you did, creating an extra boot partition. You can go on | from there like this: | | ******* WARNING ******* | You should just expect that you will run into problems. I also do this | explanation right from memory without testing (although last time I | did this, it just worked). If your system does not boot, you still can | use a rescue system to fix things. Also note that you MUST change all | the (hd?,?) entries according to your system. | *********************** | | | 1. unmount /boot | 2. mount /<boot partition> /mnt | 3. edit /etc/fstab and remove the line with /boot (or comment it) | 4. cp -a /mnt/* /boot | 5. edit /etc/grub.conf and modify it in a way that it is installed | into your root partition. For example, if your root partition is the | second partition on the first harddisk, this would look like this: | ---- | setup --stage2=/boot/grub/stage2 (hd0,1) (hd0,1) | quit | ---- | The first (hd0,1) is the pointer where to write the boot loader. | 6. edit /boot/grub/menu.lst and add /boot at the beginning of all | initrd and vmlinuz lines. For example, change | kernel /vmlinuz-2.6.18.8-0.9-default ..... | to | kernel /boot/vmlinuz-2.6.18.8-0.9-default | Also change the path to your gfxmenu (something like | gfxmenu (hd0,0)/message | to | gfxmenu (hd0,1)/boot/message | 7. run grub --batch < /etc/grub.conf | 8. look at the output! Check that no real problem occured. | 9. edit /mnt/grub/menu.lst and change the entries into something like | title openSUSE 10.2 | rootnoverify (hd0,0) | chainloader (hd0,1)+1 | 10. remove all unnecessary files in your master grub. These are all | like /mnt/vmlinu* /mnt/initrd* /mnt/config* /mnt/sym* . You must keep | /mnt/message and /mnt/grub, and I also like to keep /mnt/backup_mbr | 11. umount /mnt | 12. reboot and hope :) | | 13. For the advanced user: You also might want to add again a kernel | and a rescue system to the master grub partition. In that case, you | still have a rescue system if no other partition is bootable anymore. | | If I find time, I will also add this to the wiki, or maybe if someone | could just try and fix the problems before this goes to the wiki :). | | Berthold Thnx for the reply, seems sane enough to work. I will try to do this, because i want to get rid of overwritten grubentries for once and for all. I do not know if i make it today.... | | | -- | ------------------------------------------------------------------ | Berthold Gunreben SUSE Linux GmbH -- Dokumentation | mailto:bg@suse.de Maxfeldstr. 5 | http://www.suse.de/ D-90409 Nuernberg, Germany | SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) - -- Have a nice day, M9. Now, is the only time that exists. ~ Besturingssysteem: Linux 2.6.22.17-0.1-default x86_64 ~ Current user: monkey9@AMD64x2-sfn1 ~ System: openSUSE 10.3 (x86_64) ~ KDE: 4.0.1 (KDE 4.0.1) "release 9.1" ~ OS: Linux 2.6.22.17-0.1-default x86_64 ~ Huidige gebruiker: monkey9@AMD64x2-sfn1 ~ Systeem: openSUSE 10.3 (x86_64) ~ KDE: 3.5.7 "release 72.6" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFHvre4X5/X5X6LpDgRAj8qAJ964oPy5MaN8b4siubYo1y1ZjbHewCcCMtw ZcmaOsR0TsWNUB7ZmG41ygY= =RnZV -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org