similar to: Testing...

Especially you who are doing large-scale network booting, please try out 4.10-pre17 *and report the results*. I'm hoping with Gene Cumm's fixes that we have can promote this to a full release shortly, but I really need test reports -- good or bad. -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf.

Eric Biederman has taken the work I did almost two years ago to port lwIP to Syslinux, and actually gotten it to the point where it is integrated into the filesystem stack and *working*. As such, I have pushed out a new branch "lwip" to the git repository, for testing purposes, and I have made a 4.10-pre1 prerelease which includes this code. I don't think it is ready for prime time

Hi, I merged ldlinux.asm and extlinux.asm on the fsc branch, observing that there were very little difference between them left. So far, so good. I found, however, a test which fails on the fsc branch (with or without the merge.) I have tracked it down to vfat_mangle_name() overwriting a bunch of random .bss16 memory, eventually including the CallbackSP variable.

Hi All, I am still having troubling with PXE. Thanks for replying Shao.I did follow ur suggestions and my results have improved a bit.From Ethereal and TCPdump, I can see that the client sucessfully dowloads the file pxelinux.0 from the server but stops at this point. here is the output of tcpdump tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes 11:05:41.966864 IP

It was actually released yesterday, but due to some technical difficulties I didn't get a chance to announce it properly: Syslinux 4.03 is primarily a bug fix release. Changes in 4.03: * Don't hang if no configuration file is found. * Better support for booting from MBRs which don't pass handover information. * EXTLINUX: Try to be smarter about

Hi all, I have pushed out one more 4.03 prerelease; please help checking or testing it as I'm about to push a 4.03 out really soon. -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf.

I'm going to try to push 4.05 out this week, so please holler if there is anything critical missing. -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf.

Syslinux 4.02 is a bug fix release, but also adds an experimental new Win64 installer (syslinux64.exe), extends the new syslinux installer CLI to all the installers. Changes in 4.02: * SYSLINUX: correctly handle the case where the -d option is specified with a non-absolute path, i.e. "syslinux -d syslinux" instead of "syslinux -d /syslinux".

Sorry Gene, I got the version of binutils is 2.17. I download the latest Binutils to make the *objdump* and *objcopy*. with both of these utilities to create new pxelinux.raw. then, the error message shows me that, objcopy -O binary pxelinux.elf pxelinux.raw ../lzo/prepcore pxelinux.raw pxelinux.bin ../lzo/prepcore: pxelinux.raw: output too big (30165, max 0) make[1]: *** [pxelinux.bin] Error 1

3.75 is a bug fix release for 3.74. Changes in 3.75: * PXELINUX: fix the "keeppxe" option, which was broken in 3.74. * MEMDISK: correct the extraction of geometry information from the MBR of a hard disk image, again broken in 3.74. * extlinux(1) man page from Brian Pellin. * Simple menu: MENU SAVE is now controllable on a menu-by-menu

I have addressed all the issues that I know about (including, hopefully, the isohybrid version dependence...). I would like to release this this week so please let me know as soon as possible if this version is "go". -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf.

If there is anything that you think should have been in Syslinux 4.04 which isn't there please holler now. -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf.

So far, the consensus seem to be: - Devel list is not desirable at this time. I will continue to post major announcements to syslinux-announce, of course. - The 4-space coding standard seems to get most favor. I would like to run reformatting jobs immediately after the 3.81 release; the expectation is that other people will run the same reformatting on any code merged after that point

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

It might help to attach the attachment before sending. - Shao -----Original Message----- From: Miller, Shao Sent: Monday, March 01, 2010 09:38 To: 'For discussion of Syslinux and tftp-hpa' Subject: RE: [syslinux] isohybrid: change default offset to 1 to avoidparted troubles -----Original Message----- From: syslinux-bounces at zytor.com [mailto:syslinux-bounces at zytor.com] On Behalf

Hi all, I have released a technology preview version of the elflink branch as sylinux-5.00-pre1. It is basically functional but definitely has a fair share of rough edges. Nevertheless it would be great if people would be willing to test it out and let us know what works and doesn't work... -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak

Hi everyone, I have pushed out a development preview release of Liu's filesystems in C code (including ext4 support for EXTLINUX). It is called 4.00-pre1, which doesn't mean it is the final 4.00 by any means (it isn't even current with respect to some aspects of the 3.8x branch.) However, it is now available for people to try out. It is checked into the fsc branch

I just pushed out Syslinux 4.10-pre21. This prerelease version fixes gPXE virtio support... again, if you have had a system with problems on 4.10-preX, I would appreciate your testing it out. -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf.

Given the number of people that are starting to be involved in Syslinux development, I wanted to start a discussion about a common coding style, for C code in particular. Currently, a lot of the code in Syslinux is written in different styles, partly because my own style has changed over the years. There are pretty much two alternatives that I think are realistic: a) Linux kernel coding style:

It's time again to apply to be a mentoring organization for Google Summer of Code. This means we need to refresh the list of suggested projects at: http://syslinux.zytor.com/wiki/index.php/Google_Summer_of_Code_Ideas I'm running even more ragged than usual, so any help in this would be appreciated. I'd also like to know who'd be willing to mentor this year. -hpa -- H. Peter