search for: _isohybrid_

Quoting http://www.syslinux.org/wiki/index.php/Isohybrid#UEFI: "The additional isohybrid feature for UEFI adds a partition to the MBR partition table pointing to the same file in the ISO 9660 filesystem as does the El Torito catalog entry for EFI." According to this (and can be see using fdisk) it's being created a partition-inside-partition just by setting its start and end

...file in the ISO 9660 filesystem > > as does the El Torito catalog entry for EFI." Ady wrote: > IMHO, the current content of the Isohybrid page in the Syslinux Wiki is > not clear enough [...] The current generic information is > rather focused on _potential_ capabilities of _isohybrid_ tools and > some of their internal technical characteristics, and less focused on > actual practical steps for ends users. Well, it is about really usable capabilities of isohybrid, which regrettably only work with EFI boot software from other bootloader projects. isohybrid can mark a FAT...

...em > > > as does the El Torito catalog entry for EFI." > > Ady wrote: > > IMHO, the current content of the Isohybrid page in the Syslinux Wiki is > > not clear enough [...] The current generic information is > > rather focused on _potential_ capabilities of _isohybrid_ tools and > > some of their internal technical characteristics, and less focused on > > actual practical steps for ends users. > > Well, it is about really usable capabilities of isohybrid, Which is the same as what I just said, "potential capabilities". Yes, they...

...of copying the content of the isohybrid image I would use a dd-like method, then the device won't boot in UEFI mode since the (ISO9660) file system is not currently supported by 'syslinux.efi'. I am still of the opinion that the whole FAT "efiboot.img" issue is not about _isohybrid_, but about how GRUB2 does it. For the GRUB2 method, this "efiboot.img" is equivalent to an "El Torito no-emulation" method valid for UEFI. This is the relevant information that concerns the isohybrid tools. (In fact, the UEFI specs are not very clear for common users about t...

...660 filesystem outside of its ESP. (Ain't there any way to put enough ISOLINUX brain into the ESP so that it is smart enough ?) > _ clearly present generic capabilities of "isohybrid" images; ISOLINUX-only isohybrid is only suitable for BIOS firmware. > _ differentiate what _isohybrid_ itself can and cannot do It equips ISO 9660 filesystem images with partition tables which point to the software for the initial boot stage. It cannot create the FAT image for the EFI System Partition. > _ clarify the existence of different isohybrid variants I think that this is explained in...

...uld show a pure SYSLINUX example of UEFI isohybrid. The questions of piranna were not the first time that we had to explain our non-knowledge around ISOLINUX and UEFI. The wiki needs clarification. > I am still of the opinion that the whole FAT "efiboot.img" issue is not > about _isohybrid_, but about how GRUB2 does it. It is about what UEFI expects (without an UEFI boot manager like rEFInd involved). It wants an UEFI image, i.e. a *.efi file. Its own means of finding it are the EFI System Partitions of the devices, the NVRAM variables (e.g. manipulated by efibootmgr(8)), and the fal...

...using the /efi/boot/bootx64.efi path but instead just copied all files in the root directory of the FAT disk image, but since it already load the kernel and the initramfs maybe the canonical path is not required... is it? Do I need to use the canonical one (and why)? >> _ differentiate what _isohybrid_ itself can and cannot do > > It equips ISO 9660 filesystem images with partition tables > which point to the software for the initial boot stage. > It cannot create the FAT image for the EFI System Partition. Also add instructions about how to create a FAT image... and maybe add the ha...

...ur prior email might be relevant too. IMHO, the current content of the Isohybrid page in the Syslinux Wiki is not clear enough (in the past we have had here some discussion about the target audience of such page). The current generic information is rather focused on _potential_ capabilities of _isohybrid_ tools and some of their internal technical characteristics, and less focused on actual practical steps for ends users. The actual structure of the resulting partition table depends on the building tool in use. For example, there are several variants of the 'isohybrid' tool, and the ...

...;genisoimage ... -e" is a necessary precondition for the run of isohybrid --uefi. > Regarding current versions of the 3 tools built with cygwin, I only > know of mkisofs. I know from user feedback that GNU xorriso gets built on cygwin without problems. > For instance, should the _isohybrid_ > wiki page in Syslinux include details about ISO9660 or FAT or MBR or > partition tables? I'd say no. But it has to be mentioned that isohybrid is about adding an MBR. It is necessary to know that for --uefi the ISO image has to contain an EFI boot image, which is supposed to be a FAT...

...gt; for the run of isohybrid --uefi. > > > > Regarding current versions of the 3 tools built with cygwin, I only > > know of mkisofs. > > I know from user feedback that GNU xorriso gets built on cygwin > without problems. > > > > For instance, should the _isohybrid_ > > wiki page in Syslinux include details about ISO9660 or FAT or MBR or > > partition tables? > > I'd say no. > But it has to be mentioned that isohybrid is about adding an MBR. > It is necessary to know that for --uefi the ISO image has to contain > an EFI boot i...

...inux wiki should be helpful to common users, and not a University paper (please understand this as a generic sentence and not for this particular page or discussion). If a common user can understand the basic concept and the basic method, then we are on the right track. For instance, should the _isohybrid_ wiki page in Syslinux include details about ISO9660 or FAT or MBR or partition tables? Or about the MBR/GPT differences? Or about the backup in a GPT layout? Perhaps mentioning the possibility that their original ISO images might be slightly bigger after using the isohybrid command is relevant...

> Hi, > > i have written an introduction to isohybrid and put it on > the discussion page of the ISOLINUX wiki. > > http://www.syslinux.org/wiki/index.php/Talk:ISOLINUX#Proposal_for_description_of_isohybrid > > Review and proposals are appreciated. > > The reference to "above mkisofs command" anticipates the final > position of this text at the end

...Project cannot overcome by itself the amount of misinformation about Syslinux, booting, BIOS, UEFI and other bootloaders in general; simply there are not enough resources. > > > > I am still of the opinion that the whole FAT "efiboot.img" issue is not > > about _isohybrid_, but about how GRUB2 does it. > > It is about what UEFI expects (without an UEFI boot manager > like rEFInd involved). It wants an UEFI image, i.e. a *.efi > file. Its own means of finding it are the EFI System > Partitions of the devices, the NVRAM variables (e.g. > manipulated...