|
From: | Emilio Lazo Zaia |
Subject: | Re: Booting El Torito image from a partition table |
Date: | Sat, 28 Nov 2015 13:46:25 -0430 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:42.0) Gecko/20100101 Icedove/42.0 |
On 28/11/15 13:31, Andrei Borzenkov wrote:
The only syslinux code in my example is mbr.bin that is a generic MBR binary code to boot from the first partition which has the bootable flag. In those steps we can avoid writing syslinux's mbr.bin into /dev/loop0 and using install-mbr binary, which isn't related to syslinux and provides the same28.11.2015 19:55, Emilio Lazo Zaia пишет:Of course isohdppx.bin code and isohybrid binary are ISOLINUX specific, so we can't combine them with GRUB2. The problem here seems to be that GRUB2 boot_hybrid.img don't pass partition information to core.img because it wasn't designed to handle partitioned devices. Right?The problem is that boot_hybrid.img does not know about partition information that is passed to it by syslinux using method specific to syslinux.
functionality, coded in a different way.isolinux hybrid -partok- images (like SLAX, Debian, ...) works if MBR code is the one provided by syslinux (mbr.bin)
but also if the MBR code on the disk is installed by 'install-mbr'.
[Prev in Thread] | Current Thread | [Next in Thread] |