similar to: SYSLINUX 2.07-pre2 released

Syslinux 4.01 is a bug fix release for 4.00, but also includes the new experimental lua interpreter, as well as the ifplop module. Changes in 4.01: * ISOLINUX: fix initialization on systems which don't zero low memory. * SYSLINUX/EXTLINUX: fix handing of disk read retries in EDD mode. * ISOLINUX: change the initialization sequence to avoid

core and the simple menu do not interpret the IPAPPEND/SYSAPPEND directives in the same way. Which is the proper way? Either way, this should be clarified in the documentation. com32/elflink/ldlinux/readconfig.c: } else if ((ep = looking_at(p, "ipappend")) || (ep = looking_at(p, "sysappend"))) { uint32_t s = strtoul(skipspace(ep), NULL,

On Sun, Jun 23, 2013 at 11:09 PM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Sun, Jun 23, 2013 at 11:06 PM, Gene Cumm <gene.cumm at gmail.com> wrote: >> core and the simple menu do not interpret the IPAPPEND/SYSAPPEND >> directives in the same way. Which is the proper way? Either way, >> this should be clarified in the documentation. > > To be clear:

On Sun, Jun 23, 2013 at 11:06 PM, Gene Cumm <gene.cumm at gmail.com> wrote: > core and the simple menu do not interpret the IPAPPEND/SYSAPPEND > directives in the same way. Which is the proper way? Either way, > this should be clarified in the documentation. To be clear: core treats the value as always hexidecimal while simple menu treats it as decimal unless a 0x prefix is

On Sun, 23 Jun, at 11:21:45PM, Gene Cumm wrote: > Correction: simple menu always does decimal (as should be expected). > > >> com32/elflink/ldlinux/readconfig.c: > >> } else if ((ep = looking_at(p, "ipappend")) || > >> (ep = looking_at(p, "sysappend"))) { > >> uint32_t s = strtoul(skipspace(ep),

does the IPAPPEND option still exist? If so I want clearification on it please. Out of the syslinux documentation it says the following. The flag_val is an OR of the following options: 1: indicates that an option of the following format should be generated and added to the kernel command line: ip=client-ip:boot-server-ip:gw-ip:netmask ... based on the input from the DHCP/BOOTP or PXE boot

Hi, When we meet UEFI or EFI firmware, lots of linux os release use GRUB bootloader. But I wanna use isolinux to boot the installation environment and also the linux os installed. Some question puzzled me. Now, I look for your help: 1. I didn't found information about how to use syslinux(isolinux,etc.) in uefi. I wanna know that are there some differences of the isolinux configuration

Background: I recently wrote to Peter Anvin regarding IPAPPEND functionality, and he suggested I take the issue to this mailing list. I see it has been touched upon several times, after reviewing the archives. Let me see if I can add to it with a good level of detail: When using PXE to network boot a linux client, PXE must first acquire the client's IP address, by dhcp request, then, the

Hello, I'm having trouble PXE booting the Xen hypervisor kernel as follows: PXELINUX 3.31 0x4518b206 Copyright (C) 1994-2005 H. Peter Anvin UNDI data segment at: 00094FC0 UNDI data segment size: 4A30 UNDI code segment at: 000999F0 UNDI code segment size: 44E4 PXE entry point found (we hope) at 999F:00D6 My IP address seems to be 0A000063 10.0.0.99

After all the bug fixes over the last few weeks I thought it was high time to release 2.07. It certainly doesn't fix everything, but it fixes several important problems people have reported. Changes in 2.07: * MEMDISK: Workaround for BIOSes which go into a snit when they get a RESET command for the floppy system when there is no floppy in the system.

Hi all, I just pushed out SYSLINUX 3.72-pre2. It has a rather cool new feature: a hack to ISOLINUX to create a single image which can be booted either from CD-ROM or from what BIOS considers a hard disk medium (USB keys, etc.) -hpa

A 3rd option is missing, could it be that 4 was meant to be 3 ? IPAPPEND flag_val [PXELINUX only] The IPAPPEND option is available only on PXELINUX. The flag_val is an OR of the following options: 1: indicates that an option of the following format should be generated and added to the kernel command line:

On Wed, Dec 11, 2013 at 9:22 PM, ?? <kun.he at cs2c.com.cn> wrote: > When we meet UEFI or EFI firmware, lots of linux os release use > GRUB bootloader. But I wanna use isolinux to boot the installation > environment and also the linux os installed. Some question puzzled me. Now, > I look for your help: > > 1. I didn't found information about how to use >

On 2/7/19 4:03 AM, Joakim Tjernlund wrote: >>> >>> Hi, >>> >>> I merged your tree and added the install patch on top of it. Thank you! >>> >>> -hpa >> >> Is it worth doing another -pre immediately since upgrading gnu-efi >> took such a large leap? My thought is if someone has an issue with >> the new proposed

It appears that increasing the command line limit to 1023 caused the .bss memory area to overflow. Unfortunately NASM didn't detect this as it ought to have and therefore I didn't catch it as an error. I have dropped the command line limit to 511 characters and released it as 3.09-pre2. This is a release candidate; please test it out and if it works I'll make it 3.09. -hpa

I have released SYSLINUX 2.10-pre2. I *really* would like testing reports for this one, especially ISOLINUX, since I've included Knut Petersen's fix for Award BIOSes... Changes in 2.10: * MEMDISK: Handle images compressed with zip as well as with gzip. Some Windows-based image tools apparently generate these kinds of images by default. Patch by Patrick

On Wed, Feb 6, 2019 at 2:35 PM H. Peter Anvin via Syslinux <syslinux at zytor.com> wrote: > > On 2/6/19 9:17 AM, Joakim Tjernlund via Syslinux wrote: > > On Wed, 2019-02-06 at 16:00 +0100, Joakim Tjernlund wrote: > >> On Tue, 2019-02-05 at 14:07 -0800, H. Peter Anvin via Syslinux wrote: > >>> CAUTION: This email originated from outside of the organization. Do

On Thu, 2019-02-07 at 06:12 -0500, Gene Cumm wrote: > On Wed, Feb 6, 2019 at 2:35 PM H. Peter Anvin via Syslinux > <syslinux at zytor.com> wrote: > > On 2/6/19 9:17 AM, Joakim Tjernlund via Syslinux wrote: > > > On Wed, 2019-02-06 at 16:00 +0100, Joakim Tjernlund wrote: > > > > On Tue, 2019-02-05 at 14:07 -0800, H. Peter Anvin via Syslinux wrote: > >

On Thu, 2019-02-07 at 13:14 -0800, H. Peter Anvin wrote: > CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. > > > On 2/7/19 4:03 AM, Joakim Tjernlund wrote: > > > > Hi, > > > > > > > > I merged your tree and added the install patch

On 2/6/19 12:07 PM, Joakim Tjernlund wrote: > On Wed, 2019-02-06 at 11:56 -0800, H. Peter Anvin wrote: >> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. >> >> >> On 2/6/19 11:44 AM, Joakim Tjernlund wrote: >>> On Wed, 2019-02-06 at 11:34 -0800,