similar to: Steps to create efiboot.img file

For the sake of the discussion. Screenshots not included due size limit. ----- Forwarded message from syslinux-owner at zytor.com ----- Date: Sun, 05 Apr 2015 17:09:50 -0700 from: syslinux-owner at zytor.com To: syslinux-owner at zytor.com Subject: Syslinux post from piranna at gmail.com requires approval List: Syslinux at zytor.com From: piranna at gmail.com Subject: Re:

> Hi, > > piranna wrote: > > > 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." > > Ady wrote: > > IMHO, the

> > I am still interested in improving the isohybrid wiki > and will watch for pointers to descriptions of the FAT > production process (with GRUB/GRUB2 if not with SYSLINUX). > > If no such descriptions appear within the next weeks, > then i plan to state in > http://www.syslinux.org/wiki/index.php/Isohybrid#UEFI > > "The SYSLINUX project cannot yet provide

> 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 to be clear on the topic, I decided to do some tests from scratch on my MacBook Pro. This are the steps and results: 1. I've pick my USB pendrive and zeroed it, and after that created a new MBR partition scheme with fdisk and a VFAT partition of 32MB. Later I dd'd the file /usr/lib/syslinux/mbr/mbr.bin from SysLinux 6.03 and set the boot flag on the partition, so it could be able to

Hi, i wrote: > > Well, it is about really usable capabilities of isohybrid, Ady wrote: > but their practical combination, usage, effects, > goals... are not expressed clearly enough for the common user to put in > practice. How to express the embarrassing fact that ISOLINUX is not ready for UEFI but isohybrid is ? http://www.syslinux.org/wiki/index.php/Isohybrid#UEFI would

> The third boot image is HFS+, not FAT. > I understand this is for pre-EFI Macs. Apple started usinf EFI when it switched to Intel x86 CPUs, previous to this ones it was using OpenFirmware in their PowerPC "new world" machines (IBM PowerPC G4 & G5). > Try a Debian amd64 ISO, e.g.: >

> isohybrid violates UEFI by combining both methods and > by nesting partitions. The motivation for this is given by > Matthew Garrett in > http://mjg59.dreamwidth.org/11285.html There it says about creating a third El Torito image only for Macs, since old ones could fail and this could be the problem I'm having. I've used the --mac option of IsoHybrid and it's demanding

Hi, Some lines are printing on console: [CCafException] CAppConf@[1711]: CommAmqpListener: [CCafException] CAppConfig:: getString() Required config parameter [amqp_password] is missing from section [c ommunication_amqp] Can you help me to understand why we are getting these lines on console? How we can remove these lines from the console? Please suggest. Thanks & Regards, Shagun

Hi, I am trying to built an ISO with nodejs010 packages but when I run the command "repoclosure -a x86_64 -r <local-repository-name>" to check its further dependencies, it is giving unresolved dependencies error. Example: package: nodejs010-node-gyp-3.2.0-2.el7.centos.noarch from Harman (it's a local repo name) unresolved deps: npm(minimatch) < 0:4

Lmgtfy returns: https://communities.vmware.com/thread/532962 Something to do with VMware?s agent? -- Jonathan Billings > On May 30, 2018, at 11:38, Maheshwari, Shagun <Shagun.Maheshwari at Harman.com> wrote: > > Hi, > > Some lines are printing on console: > [CCafException] CAppConf@[1711]: CommAmqpListener: [CCafException] CAppConfig:: getString() Required config

Hi, Curt Brune wrote: > At the risk of contributing to the 'urban legends' and the 'salads' I apologize to all communities who hand out correct info. :)) > http://lukeluo.blogspot.com/2013/06/grub-how-to-2-make-boot-able-iso-with.html Well, the excursion on CD-DA is off topic and i would describe many aspects in different terms. Nice to see that at least one person read

> Would it be desirable to explain how Fedora et.al. > created their FAT boot images by help of old or new > GRUB ? > (If developers of EFI bootable ISOs are reading this, > please give a short sketch of the procedure.) I did it by including the Linux kernel and the initramfs, but that's sub-optimal since I need to have them in two places. That's why I asked about re-using

> None of the ISOs i know has this stuff in the FAT image. > There must be some way for GRUB/GRUB2 to escape from FAT > into the ISO. > debian-7.7.0-amd64-netinst.iso does the job by a > bootx64.efi binary of 421888 bytes. It's the only file > in the FAT (of 458752 bytes). I'll try to use it to see if it works. > It might be a workaround for ISOLINUX to bring

On Sun Apr 05 15:17, Thomas Schmitt via Syslinux wrote: > None of the ISOs i know has this stuff in the FAT image. > There must be some way for GRUB/GRUB2 to escape from FAT > into the ISO. > debian-7.7.0-amd64-netinst.iso does the job by a > bootx64.efi binary of 421888 bytes. It's the only file > in the FAT (of 458752 bytes). [ long time syslinux user -- thanks all!! ] At

Hi, > 6. Renamed back /EFI/boot/bootx64.efi to /EFI/boot/syslinux.efi, just > to be sure. The "Default fallback loader on 32 MiB device" entry has > changed to "Syslinux on 32 MiB device". How the hell does it know that it is "Syslinux" ? The same file content does not cause that name if it is presented under the default name. Does EFI just guess

Hi, i wrote: > > Does EFI just guess "Syslinux" from "syslinux.efi" ? piranna at gmail.com wrote: > Maybe EFI, but I think it's rEFInd, > http://www.rodsbooks.com/refind/ Oh, a man in the middle with extra brains. This explains a lot. >From what storage device does it boot ? (From hard disk ?) Will it be present with the production images ? > > I

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

> The most annoying thing (to me) is that it doesn't boot at all on > Legacy OS mode (MBR), while it should... :-/ No, it shouldn't. If you are initially booting in (U)EFI mode (into rEFInd, or some EFI shell or any other EFI boot loader or EFI boot manager), then generally speaking you are expected to boot in EFI mode. But some (U)EFI firmware _might_ be able to

Hi, i wrote: > > Would it be desirable to explain how Fedora et.al. > > created their FAT boot images by help of old or new > > GRUB ? > > (If developers of EFI bootable ISOs are reading this, > > please give a short sketch of the procedure.) piranna at gmail.com wrote: > I did it by including the Linux kernel and the initramfs None of the ISOs i know has this