similar to: SYSLINUX 3.70-pre1: development release

Hello everyone, I have just released SYSLINUX 3.70, which is the first version which includes gPXE for support of non-TFTP network scripts, as well as a large number of other enhancments. gPXE support is still somewhat experimental - in particular it still doesn't support chaining other NBPs. Very special thanks to: - rPath, Inc, my employer, for the uncountable hours I've spent

Could we just activate FTP on gpxe ? I did a trivial patch for enabling it on top of 3.72-pre1. Thanks, Erwan --- gpxe/src/config.h.old 2008-09-03 09:40:47.055018406 +0200 +++ gpxe/src/config.h 2008-09-03 09:40:54.728065911 +0200 @@ -94,7 +94,7 @@ #undef DOWNLOAD_PROTO_NFS /* Network File System */ #define DOWNLOAD_PROTO_HTTP /* Hypertext Transfer Protocol */ #undef

I have just pushed out SYSLINUX 3.70-pre8. The two main differences is that I have updated the gPXE source base, and added a sanboot module (sanboot.c32). sanboot.c32 *should* be capable of initiating an iSCSI or AoE boot, but I haven't actually tested it. The other main difference is that gPXE now advertises HTTP/1.0 instead of HTTP/1.1, since the code was not actually HTTP/1.1

From: Vicente Jimenez Aguilar <googuy at gmail.com> tftp tsize option don't needed anymore starting at version 3.70 --- doc/pxelinux.txt | 1 - 1 files changed, 0 insertions(+), 1 deletions(-) diff --git a/doc/pxelinux.txt b/doc/pxelinux.txt index 8d0792f..94d7649 100644 --- a/doc/pxelinux.txt +++ b/doc/pxelinux.txt @@ -405,7 +405,6 @@ load PXELINUX. See: The following problems

I have pushed out SYSLINUX 3.73-pre1. It only contains the build fixes that have accumulated since 3.72, and a version bump of gPXE to the equivalent of the 0.9.5 gPXE release. Given the number of people who have had build problems, I'm making this a release candidate, with the intent of pushing out 3.73 as a minor fixes release only. If you have the ability to test 3.73-pre1,

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

Folks, I've just released the first prelease for the 5.10 series. The intention is to leave 5.02-pre3 where it is and move to 5.10-pre1. The only difference between 5.02-pre3 and 5.10-pre1 is the merge of the lwip branch (and a single commit to fixup the -DDEBUG=2 build), which warranted a bump in the version minor number. See the shortlog below for details of the differences between

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

I post this to the mailing list, but perhaps is not the good place. I'm not subscribed, so I don't know if I'm going to get any reply, but please, tell me where to send patches. I attach two patches that correctly describes the new support for F11 and F12 in documentation but I have two more question to update documentation accordingly. In doc/syslinux.txt line 515, talking about

Okay guys, This is separate from my last few messages. Along with those attempts, I decided to migrate from pxelinux.0 to gpxelinux.0 in my existing setup. Admittedly I haven't tried previous gpxelinux.0's but I am willing to if someone thinks it would be useful. Everything works as expected with pxelinux.0 of the same version. With gpxelinux.0: TFTP Prefix: Trying to load:

Hello everyone I am experiencing problems with PXELinux/gPXE when netbooting using HTTP. The problems I encounter: - When the intel bootROM is sending out a DHCPDISCOVER it might not recieve an IP address, but the server did send out a OFFER. Capturing packets reveals the packets have been sent, and the client _should_ have recieved it. But when it passes that stage: - When the gPXE bootROM is

I forgot tftp32 log. Here it is, starting from "default" file request: Connection received from 192.168.1.20 on port 57099 [31/05 10:51: 29.370] Read request for file <pxelinux.cfg/default>. Mode octet [31/05 10:51:29.370] OACK: <tsize=938,> [31/05 10:51:29.420] Using local port 1286 [31/05 10:51:29.420] Connection received from 192.168.1.20 on port 57100 [31/05

I am attempting to setup a test gpxe(linux.0) http site, to test among other things the recent dynamic option 252 solution. In the process of investigation I stumbled across http://www.etherboot.org/wiki/appnotes/authmenus which indicates the gpxe can launch vesamenu.c32 directly. Various other pages on etherboot's site indicate menu.c32/vesamenu.c32 can be used independently as well.

Hi all, I have just released syslinux-3.70-pre25. Unless someone has something big and scary that either I have managed to miss or was just stumbled over, I'm going to release 3.70 final some time between tomorrow and Monday. Thus, *please holler now* if there are any stop-ship problems still known... -hpa

I made other tests. It's not a matter of Win98 versus WinXP, things change passing from tftpd32 v310beta to v3.33. This version seems to work fine, but the logs show problems. Here is the complete log with pxelinux 3.82-pre4: Rcvd DHCP Discover Msg for IP 0.0.0.0, Mac 00:1E: 68:A6:9E:A9 [05/06 18:24:43.816] DHCP: proposed address 192.168.1.20 [05/06 18:24:43.816] 1356 Request 2 not

... > nasm -f elf -Ox -g -F dwarf -DDATE_STR="''" \ > -DHEXDATE="0x56dc3c62" \ > -Di386 \ > -I/tmp/syslinux-6.04-pre1/core/ \ > -l ldlinux.lsr -o ldlinux.o -MP -MD ./.ldlinux.o.d /tmp/syslinux-6.04-pre1/core/ldlinux.asm > nasm -f elf -Ox -g -F dwarf -DDATE_STR="''" \ > -DHEXDATE="0x56dc3c62" \ > -Di386 \ >

On 06.03.2016 18:23, poma wrote: > On 06.03.2016 16:47, poma wrote: >> ... >>> nasm -f elf -Ox -g -F dwarf -DDATE_STR="''" \ >>> -DHEXDATE="0x56dc3c62" \ >>> -Di386 \ >>> -I/tmp/syslinux-6.04-pre1/core/ \ >>> -l ldlinux.lsr -o ldlinux.o -MP -MD ./.ldlinux.o.d /tmp/syslinux-6.04-pre1/core/ldlinux.asm >>>

Hello everyone, I have released SYSLINUX 3.63. The main update is a fix to EXTLINUX, which would get confused by directories with deleted file entries. Special thanks to Stas Kysel of rPath, Inc. for spotting this problem and giving me an excellent test case; and of course to rPath, Inc. in general for being my employer and being extremely supportive of my SYSLINUX work! I have also

This is 100% functionally equivalent to 3.54-pre1, with only a few minor documentation changes. Changes in 3.54: * Add "menu separator", "menu indent", "menu disabled" (see README.menu). * vesamenu: fix handing of VESA modes with noncontiguous memory buffers. In particular, Qemu/KVM sets up such a mode when Cirrus

Network UPS Tools version 2.2.2-pre1 has been released. http://www.networkupstools.org/ Direct access: - Download: http://www.networkupstools.org/source/2.2/testing/nut-2.2.2-pre1.tar.gz - News: http://www.networkupstools.org/source/2.2/testing/new-2.2.2-pre1.txt - ChangeLog: http://www.networkupstools.org/source/2.2/testing/ChangeLog Arnaud and the NUT team -- Linux / Unix Expert R&D -