RE: Re: [opensuse] Help with "blind" os-prober
-----Ursprüngliche Nachricht----- Von: Andrei Borzenkov Gesendet: Do. 26.11.2015 18:08 An: opensuse@opensuse.org Betreff: Re: [opensuse] Help with blind os-prober
26.11.2015 19:22, stakanov@freenet.de пишет:
ypted (in ext4)
And you are using BIOS, no UEFI? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----Ursprüngliche Nachricht Ende-----
You see me smiling there. This is a 939 mainboard from 2006. I used it up to now with 13.2. At that time, suse was 9.1, Sata was 1.5 mainly, Sata II was fancy, AM2 processor the near future and I was still young and had a life. MS did not even have had the bad idea of UEFI. And the "Matrix" was on display, brand new. Just Bios. I did send you a link to the reference manual of the board so you get an idea of somewhat still good but also historical technology. The boot goes over bus mastering from a PCI controller to the mainboard BIOS. It is the BIOS of the promise controller (PCI) that handles and manages the discs. So, no, no UEFI. --- Alle Postfächer an einem Ort. Jetzt wechseln und E-Mail-Adresse mitnehmen! http://email.freenet.de/basic/Informationen -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
26.11.2015 22:24, stakanov@freenet.de пишет:
Just Bios.
First you need UUID of "another" boot partition and for completeness relative path (it may not be that trivial in case of btrfs ...) and other things ... which is BTW exactly what grub-mkconfig does for you :) You can of course skip all this if you know this already. mount /dev/sdb1 /mnt grub2-probe -t partmap /mnt/grub2/i386-pc/core.img => msdos grub2-probe -t fs /mnt/grub2/i386-pc/core.img => ext2 grub2-probe -t fs_uuid /mnt/grub2/i386-pc/core.img => 29cd03d7-ccb1-46cb-ae23-4c015c3310e5 grub2-mkrelpath /mnt/grub2/i386-pc/core.img => /grub2/i386-pc/core.img and you ideally need unique identifier so your menu entry can be distinguished from any other uuidgen => aa679e54-d81d-4464-a30a-f9bbc8b214c4 Now add /boot/grub2/custom.cfg with content menuentry "Another openSUSE bootloader" --class opensuse --id custom-aa679e54-d81d-4464-a30a-f9bbc8b214c4 { insmod part_msdos insmod ext2 search --fs-uuid 29cd03d7-ccb1-46cb-ae23-4c015c3310e5 --set multiboot /grub2/i386-pc/core.img } This should load and launch grub2 used by "another" OS instance together with its menu. You can also use chainloader to load boot block if you know where you installed it :) Downside is, there is no reliable way to identify disk at run-time, so above is probably more generic and fool proof. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (2)
-
Andrei Borzenkov -
stakanov＠freenet.de