similar to: Syslinux 3.85-pre7: new tool "sysdump"

Syslinux 3.85 is a bug fix and minor new feature release. The biggest change is undoubtedly that gPXELINUX is now considered feature complete, and should be able to be a drop-in for PXELINUX for all uses. Special thanks to Intel Corporation, my current employer, for their support for my Syslinux work. Changes in 3.85: * gPXELINUX: updated to gPXE 1.0.0. gPXELINUX can now do NBP

This is an attempt to avoid potential confusion. Here are some example sizes for the two Syslinux versions mentioned in the e-mail subject. Your build results might be different. 4.06: 1 55 Sep 22 22:23 modules/int18.com 1 108 Nov 1 18:07 version.mk 1 138 Nov 1 18:07 version.gen 1 138 Nov 1 18:07 version.h 1 239 Sep 22 22:23 modules/poweroff.com 1 408 Sep 22 22:25

Op 20100701 om 18:15 schreef syslinux-bot for H. Peter Anvin: > Commit-ID: 18de1534f9b69fb298a5b56e61919130d875b34b > Gitweb: http://syslinux.zytor.com/commit/18de1534f9b69fb298a5b56e61919130d875b34b > Author: H. Peter Anvin <hpa at linux.intel.com> > AuthorDate: Thu, 1 Jul 2010 18:12:41 -0700 > Committer: H. Peter Anvin <hpa at linux.intel.com> >

I have produced a first cut of integrating gPXE with PXELINUX. This builds, in addition to the usual pxelinux.0, an image called gpxelinux.0 which includes the gPXE network stack. The result is that one can now download images via (almost) any network protocol supported by gPXE, including http. This lets one do fun things like using a CGI or PHP script for the configuration file. SAN

It say to give a copy of dmidecode or sysdump if I need to use localboot -1 pxelinux.0 worked with localboot 0 but gpxelinux.0 didn't it needed localboot -1 This was on my hp machines

Hi, Gene Cumm wrote: > > 3) It feels like this is a moving target where gcc keeps changing and > > different results get reported. Do we have indications that different versions of gcc5 cause different behavior on the same build and boot machines ? Ady wrote: > Since the issue is only present on specific > hardware / firmware, whatever might seem to "solve" the

make -r -C /mlsyslinux -f /mlsyslinux/Makefile SRC="/mlsyslinux" \ OBJ=/mlsyslinux objdir=/mlsyslinux bios make[1]: Entering directory `/mlsyslinux' make -r -C /mlsyslinux/bios -f /mlsyslinux/Makefile SRC="/mlsyslinux" \ objdir=/mlsyslinux/bios OBJ=/mlsyslinux/bios HAVE_FIRMWARE=1 \ ARCH=i386 LDLINUX=ldlinux.c32 all make[2]:

Hello all, I have just released SYSLINUX 3.62. This is almost identical to 3.62-pre16, with a small number of changes to the Makefiles and documentation. The focus of this release has largely been removing build-in limitations as much as possible. Quite a bit of work has gone into it. I'd like to specially thank my employer, rPath Inc.; I've spent a lot of time on this I wouldn't

From: Matt Fleming <matt.fleming at linux.intel.com> Move the MCONFIG files into a mk/ directory and give them more descriptive names. This is purely a cosmetic change to make the 'include' directives a bit more coherent by making it obvious exactly which MCONFIG file we're including. For example, in com32/lua/src/Makefile we exchange the line, include ../../MCONFIG for the

It has been observed that binaries contents are depending on the order of linked objects. This order is caused by GNU make's wildcard function and the position of sources on filesystem. This change tries to prevent this kind of randomness. Also consider building using -j1 flag to make it even more reproductible. Change-Id: Ie8eee7f336e6f1fa2863c4150d967afd15519f1d Bug:

Howdy, I just did a build on my CentOS 5.2 (x86_64) system and noticed the following error msg. I don't think this is a problem for me but I wanted the developers to be aware of it. Regards, and thanks for your time, George... make[1]: Leaving directory `/tools/pxelinux/syslinux-3.72/utils' ls -l version.gen version.h version.mk mbr/mbr.bin mbr/gptmbr.bin core/pxelinux.0

After way too long, a new production release of Syslinux is finally available. Syslinux 4.04 is primarily a bug fix release, but with some new features. Changes in 4.04: * PXELINUX: Fix handling of unqualified DNS names. * PXELINUX: Fix timer bug when PXELINUX might be unloaded (Gene Cumm). * core/writedec.inc: Fix duplicate declaration and overflow

Hi, First of all thank you so much for your prompt suggestions/help. I really appreciate this. Here is the syslinux.cfg which works perfect with syslinux-4.06 ---- PROMPT 0 TIMEOUT 50 SERIAL 0 DEFAULT mylabel LABEL mylabel KERNEL vmlinuz0 APPEND initrd=initrd.img root=/dev/mmcblk0p2 rootwait rootfstype=ext3 console=tty0 console=ttyS0,9600 ---- To further round off the error possibilities I used

Still interested in pre-compiled binaries for 6.03-pre6. But my comment about 6.02 TFTP brokenness may speak more to my lack of understanding of the TFTP protocol than to any pxelinux 6.02 code problems. It seems that when TFTP sends an OACK back to syslinux.efi, it sends it from another port than 69. So, it seems to be opening a data connection back to the TFTP client off an ephemeral port.

On Thu, Jul 4, 2013 at 10:44 AM, Shantanu Gadgil <shantanugadgil at yahoo.com> wrote: > On Thu, 7/4/13, Matt Fleming <matt at console-pimps.org> wrote: > > Subject: Re: [syslinux] Syslinux 5.11-pre7 not working > To: "Shantanu Gadgil" <shantanugadgil at yahoo.com> > Cc: syslinux at zytor.com > Date: Thursday, July 4, 2013, 4:51 PM > > On

Hello, I saw this in the release notes for 4.00: "PXELINUX: TFTP URL syntax (tftp://) supported even when not running gPXE/gpxelinux" I can't find any info describing this new functionality (searched wiki and mailing list), I'm guessing you can now use tftp:// in the paths, e g: LABEL mylabel KERNEL tftp://servername/path/to/mykernel APPEND myoptions Correct? I've

-------------------------------------------- On Sun, 10/20/13, Gene Cumm <gene.cumm at gmail.com> wrote: Shantanu, could you please try v6.02?? Your scenario failed on my OptiPlex 760 but with 6.02, it works. See also http://bugzilla.syslinux.org/show_bug.cgi?id=19 Nope, still no joy on the physical machines. Different symptoms though. On the physical machines: The HTTP starts

On Wed, 03 Jul, at 11:22:27PM, Shantanu Gadgil wrote: > Hi, > > I am a happy user of version 4.06 and have been hoping to upgrade the 5.x series (for the HTTP bits). > I have the following problems with the 5.11-pre7 build: > > 1. TFTP load is horribly slow ... even when the two REAL machines are connected to the same switch. > For a typical RHEL installation, the vmlinuz

Gene, Where did you find the precompiled binaries for syslinux 6.03-pre7? Actually, I'm interested in the pre-compiled binaries for syslinux 6.03-pre6. I went out to kernel.org, but the latest they have is 6.02. Which appears to have an endian problem in its TFTP client code (when syslinux.efi tries to connect to the TFTP server, attempts to connect to UDP port 17664 instead of 69).

-------------------------------------------- On Thu, 7/4/13, Matt Fleming <matt at console-pimps.org> wrote: Subject: Re: [syslinux] Syslinux 5.11-pre7 not working To: "Shantanu Gadgil" <shantanugadgil at yahoo.com> Cc: syslinux at zytor.com Date: Thursday, July 4, 2013, 4:51 PM On Wed, 03 Jul, at 11:22:27PM, Shantanu Gadgil wrote: > Hi, > > I am a happy