similar to: SYSLINUX 2.08-pre7 released

It's pretty much the same as 2.08-pre11. 2.08 mostly a collection of minor enhancements. Changes in 2.08: * Add new configuration command "ontimeout" to allow timeout to have a different action than just pressing Enter. * Add new configuration command "onerror" to allow a custom command to be executed in case the kernel image is not

Ok folks... SYSLINUX 2.08-pre7 is hereby declared a release candidate. Please test it out; if it works for people I'll promote it to 2.08. -hpa

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

Goodness, how many prereleases has there been in the last week... have lost count... Anyway, I have implemented the already-promised chainbooting API, and have included a sample program to chainboot floppies (it works for harddisks too, but only for the MBR.) As a bonus, in the process I actually discovered that booting .bs/.bss images under SYSLINUX was actually broken... that has been

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

I'm going to promote SYSLINUX 3.32-pre7 to release candidate unless someone objects, with the intent of releasing 3.32 immediately after Christmas. Please let me know if there are problems that should make me *not* do so, even if you have previously reported them. -hpa

So I realized I really need a better way to collect information from problematic machines, so I spent today rewriting the old memdump tool into a new "sysdump" tool. sysdump can write its output either to a serial port using ymodem[1] or over the network using TFTP *if* it was booted from the network, using PXELINUX. John R.: I would obviously like you to try this on the machine that

Well, SYSLINUX 3.50 has been in development since September of last year (it was originally a branch off 3.31), and the diff against 3.36 is almost 15,000 lines. I doubt it's going to be bug free, but prereleases can only get you so far with respect to testing. Thus, it's time to push the button and getting this thing out into the world. I hereby announce SYSLINUX 3.50. Special thanks

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

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

I just found a rather embarrassing bug in PXELINUX -- and what's worse -- I wrote an email about it and killed it off accidentally :-/ It appears PXELINUX doesn't free its internal socket buffers (it has 32 of them) when it gets an error reply from the server, including "file not found." This means it will eventually run out of sockets and "go deaf." This

Hi all, I have merged Tim's patches to the mboot loader, and have pushed it out as 3.20-pre7. I guess I'm going to actually have to make a 3.20 here soon... -hpa

I just uploaded SYSLINUX 3.72-pre7. I'm hoping this will be the final 3.72 prerelease. Please test it and holler if something is (still) broken. -hpa

I have just pushed out Syslinux 3.80-pre7. I am slightly concerned about putting this into the release tree at this point: I was working with some of the shuffler code, and found that the memory map handling was actually severely buggy on some of my test cases. Resolving that problem took rewriting most of syslinux_add_memmap(). However, against better judgement :) I decided to check in the

Hi all, I have just pushed out SYSLINUX 3.55-pre5 and 3.60-pre7. I have decided to give them both release candidate status, with the intent of having a simultaneous 3.55 (bug fixes only) and 3.60 (new functionality) release. Please test them out and let me know how they do. -hpa

Hi all, I've decided to move SYSLINUX 3.30-pre7 to release candidate status (the difference from 3.30-pre6 is pretty much that 3.30-pre7 contains a very simple compiled-in graphical background if the user doesn't specify MENU BACKGROUND.) Please test it out and let me know. Thanks, -hpa

... it has a slightly modified version of Paul's VKernelBuf initialization patch. I modified it to initialize the whole buffer instead. I found, on careful reading of the spec, that it's actually possible to patch the DHCP packets in PXE memory. This might help the handling of NBP chainloading in PXELINUX, by making the pathname of the chainloaded file available to itself. I

Tim Legge has passed the following message on to me: hpa wrote: > Quinn wrote: > > Now it seems I have found a bug in PXELINUX with regards to etherboot. > > Up until 2.07 pxelinux was responsive to the keyboard. From 2.08 and > > up the keyboard is locked at the boot prompt when pxelinux is loaded > > via etherboot 5.3.14. > > That would not be a PXELINUX bug,

Hi all, I have finally gotten SYSLINUX 3.50 what it feels like feature-complete for release, or something pretty close to it. As a consequence, I am declaring 3.50-pre16 a release candidate. Here is what's news since 3.36: Changes in 3.50: * New keywords allow the type of file to be specified in the configuration file. * It is now supported to load a different