Folks,
Finally, Syslinux 5.10 has been released. This release includes a merge
of the 4.10 development branch, which means that there's a new network
stack availble, based on the lwIP embedded TCP/IP stack. The jump from
the previous 5.01 release to 5.10 may be a little confusing, but a new
network stack is such a large change that it deserved a significant bump
in the version minor number.
To use the new stack you'll need to deploy lpxelinux.0. Using
lpxelinux.0 gets you support for HTTP/FTP out of the box. The legacy
stack is still available as pxelinux.0.
Also a number of regressions have been fixed that were introduced in
Syslinux 5.00. The shortlog appended below shows the changes since
Syslinux-5.10-pre1 because I've just realised I didn't send an
announcement for -pre2.
There are still a number of fairly important bugs that are causing
people issues and unfortunately I haven't had the time to fix them in
this release. But they are still on the TODO list.
---
H. Peter Anvin (3):
pxe: disentangle the legacy and lwip stacks without #ifdef
font: load data as a single block
serial: Clean up and abstract handling of serial ports
Josh Triplett (1):
Fix support for Linux kernel images with no protected mode code
Matt Fleming (12):
ldlinux: Always update ConfigName when opening a config file
readconfig: Don't display "(null)" labels when hitting TAB
Partially revert "pxe: Pass absolute path to pxe_chdir()"
ldlinux: Fixup lwip merge botch
pxe: Fix compiler warnings and real bug
load_linux: update errno before returning
linux: Clear up error message
font: increment pointer to fontbuf by font height
serial: fix SERIAL directive for ports > 0
font: write to 'fontbuf', not random memory
NEWS: Clarify network stack files
NEWS: Mention noteworthy changes in 5.10
--
Matt Fleming, Intel Open Source Technology Center
On 06/04/2013 06:16 PM, Matt Fleming wrote:> Folks, > > Finally, Syslinux 5.10 has been released. This release includes a merge > of the 4.10 development branch, which means that there's a new network > stack availble, based on the lwIP embedded TCP/IP stack. The jump from > the previous 5.01 release to 5.10 may be a little confusing, but a new > network stack is such a large change that it deserved a significant bump > in the version minor number. > > To use the new stack you'll need to deploy lpxelinux.0. Using > lpxelinux.0 gets you support for HTTP/FTP out of the box. The legacy > stack is still available as pxelinux.0. > > Also a number of regressions have been fixed that were introduced in > Syslinux 5.00. The shortlog appended below shows the changes since > Syslinux-5.10-pre1 because I've just realised I didn't send an > announcement for -pre2. > > There are still a number of fairly important bugs that are causing > people issues and unfortunately I haven't had the time to fix them in > this release. But they are still on the TODO list. > > --- > > H. Peter Anvin (3): > pxe: disentangle the legacy and lwip stacks without #ifdef > font: load data as a single block > serial: Clean up and abstract handling of serial ports > > Josh Triplett (1): > Fix support for Linux kernel images with no protected mode code > > Matt Fleming (12): > ldlinux: Always update ConfigName when opening a config file > readconfig: Don't display "(null)" labels when hitting TAB > Partially revert "pxe: Pass absolute path to pxe_chdir()" > ldlinux: Fixup lwip merge botch > pxe: Fix compiler warnings and real bug > load_linux: update errno before returning > linux: Clear up error message > font: increment pointer to fontbuf by font height > serial: fix SERIAL directive for ports > 0 > font: write to 'fontbuf', not random memory > NEWS: Clarify network stack files > NEWS: Mention noteworthy changes in 5.10 >Nice, thanks for this release. I guess can be a good time, to take again issues with PXE booting with special dhcp-options 209, 210, that I recently tested with 5.10 (but using the new stack) and still fails. Sending details again in a new message if needed... PS: gpxelinux.0 looks broken, at least on qemu-1.5.0, the machine is rebooted automatically, too quickly to read what happens. (lpxelinux.0 and pxelinux.0 works) -- Gerardo Exequiel Pozzi \cos^2\alpha + \sin^2\alpha = 1 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 555 bytes Desc: OpenPGP digital signature URL: <http://www.zytor.com/pipermail/syslinux/attachments/20130605/a1b657bc/attachment.sig>
On 06/04/2013 09:58 PM, Gerardo Exequiel Pozzi wrote:> > Nice, thanks for this release. > > I guess can be a good time, to take again issues with PXE booting > with special dhcp-options 209, 210, that I recently tested with > 5.10 (but using the new stack) and still fails. Sending details > again in a new message if needed... > > PS: gpxelinux.0 looks broken, at least on qemu-1.5.0, the machine > is rebooted automatically, too quickly to read what happens. > (lpxelinux.0 and pxelinux.0 works) >We should drop the bundled gpxelinux.0. It uses a very slightly forked and ancient gPXE snapshot; stock iPXE is better, but I suspect it is better to just have people get iPXE from iPXE... -hpa
On Wed, Jun 5, 2013 at 12:58 AM, Gerardo Exequiel Pozzi <vmlinuz386 at yahoo.com.ar> wrote:> On 06/04/2013 06:16 PM, Matt Fleming wrote: >> Folks, >> >> Finally, Syslinux 5.10 has been released. This release includes a merge >> of the 4.10 development branch, which means that there's a new network >> stack availble, based on the lwIP embedded TCP/IP stack. The jump from >> the previous 5.01 release to 5.10 may be a little confusing, but a new >> network stack is such a large change that it deserved a significant bump >> in the version minor number.> Nice, thanks for this release. > > I guess can be a good time, to take again issues with PXE booting with > special dhcp-options 209, 210, that I recently tested with 5.10 (but > using the new stack) and still fails. Sending details again in a new > message if needed...Using pxechn.c32, I'm having no issues with options 209/210 to Syslinux-5.10 official core/pxelinux.0 or core/lpxelinux.0. Is there any chance you could do a packet capture? I'm going to try to get an experiment with forcing these options but not sure my dhcpd will comply. -- -Gene