similar to: How to install manually?

>> could it be implemented? If that's not possible, what's doing SysLinux > > Consider bios/mtools/syslinux Just what I needed, thanks! :-D I have not seen any reference to that on the wiki docs, maybe it would make sense to add a little note about it? And regarding to the extra modules (menu.c32 and so), I need to add them previously by hand, isn't it? Just to be sure...

For testing purposses, I'm trying to hook on QEmu an ISO image that start automatically with syslinux (just a DEFAULT label and no TIMEOUT option) and change the kernel arguments to redirect the console to a serial port instead of the screen. So far I've seen that the SERIAL statement give me a welcome message and the loading of the kernel and initramfs on the serial port (but curiously,

On Wed, Dec 21, 2016 at 10:51:16AM -0500, Gene Cumm via Syslinux wrote: > On Wed, Dec 21, 2016 at 4:16 AM, piranna at gmail.com <piranna at gmail.com> wrote: > >>> could it be implemented? If that's not possible, what's doing SysLinux > >> > >> Consider bios/mtools/syslinux > > > > Just what I needed, thanks! :-D I have not seen any

I'm developing my own Linux-kernel OS (https://github.com/NodeOS/NodeOS) and I have been able to build a live ISO using IsoHybrid. Point is, it doesn't work on my MacBook Pro (Quad-core, 2.66GHz, 8GB), only on BIOS-based PCs. rEFInd show a new "Legacy OS" entry for the pendrive, but after some seconds it shows the "Not found Operating System -- Insert boot disk and press any

> 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.: >

Sorry for the delay, missed the emails. >> > Just what I needed, thanks! :-D I have not seen any reference to that >> > on the wiki docs, maybe it would make sense to add a little note about >> > it? > > Yes, http://www.syslinux.org/wiki/index.php?title=The_Syslinux_Project > is indeed a wiki. So please add you think that is missing. I was following the

Hi, i wrote: > > http://mjg59.dreamwidth.org/11285.html piranna at gmail.com wrote: > 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. The third boot image is HFS+, not FAT. I understand this is for pre-EFI Macs. Try a Debian amd64 ISO, e.g.:

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

> Sorry for the delay, missed the emails. > > >> > Just what I needed, thanks! :-D I have not seen any reference to that > >> > on the wiki docs, maybe it would make sense to add a little note about > >> > it? > > > > Yes, http://www.syslinux.org/wiki/index.php?title=The_Syslinux_Project > > is indeed a wiki. So please add you think that

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:

> 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

> 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

> Anybody show me a pure SYSLINUX isohybrid ISO that boots via EFI > and i will be able to dissect it and hopefully derive knowledge > for the wiki. Well, besides the fact that after loading the kernel and the initram it didn't started the boot process (don't know why), this is what I achieved by using a disk image with syslinux.efi... :-) -- "Si quieres viajar alrededor

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

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, > 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, 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

> 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: > > 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