similar to: [PATCH 3/5] tftp tsize option don't needed anymore starting at version 3.70

Included 3 patches that updates documentation. This completes a 5 patches set. If you prefer me to resend all of then as one patch, attached, discussing or whatever, your're welcome. Best regards, vicente >From 7cec3ad78c8454408c8b6a1950d441e02d56d138 Mon Sep 17 00:00:00 2001 From: Vicente Jimenez Aguilar <googuy at gmail.com> Date: Fri, 23 Jan 2009 00:57:48 +0100 Subject: [PATCH]

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

this may be a strange question but... i want to do some testing of tftp with and without tsize option. is there a way to start in.tftpd without enabling the tsize option? or will i have to install new tftp server that does not support tsize option? perhaps this? /usr/sbin/in.tftpd -r tsize

Perhaps a stupid question, but I've read through the changelog and the e-mail archive and can find no answer. I'm wondering why "tsize" is a necessity. Seems like the TFTP protocol correctly handles EOF. Does the code need to know in advance how large the file is going to be? If it just happens to have been written this way, would you be open to a change which eliminates the

Hi all, I have pushed out a prerelease of one of the development branches (I currently have three development branches open), 3.70-pre1. This release revamps a whole lot of internal APIs to support reading files without knowing their length ahead of time. This is necessary in order to support network protocols which do not advertise the transfer size. The immediate user-visible change is

Let's try to get this thing released. Dag: will you do your RPM buildathon on this drop? Changes in 3.74: * New UI directive, which allows a more natural way to specify a menu system (or not.) With the UI directive specifying the menu system, the DEFAULT directive can be used to select the default entry inside the menus. * kbdmap.c32: new module

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

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

Well, here it is. This is a historic Syslinux release -- it's the first one in 15 years in which the majority of the work was not done by myself; mostly because of the *huge* effort Erwan and Pierre have put in on HDT. I also want to give a special thank you to my new(ish) employer, Intel Corporation, for letting me continue to work on Syslinux. :) From here, onward and upward. I

Hi I've published my Asterisk/foneBRIDGE2/heartbeat setup: config files, scripts... along with a brief description of the architecture and working of the cluster. It's available here: http://www.bisente.com/blog/2007/08/26/asterisk-cluster-fonebridge2/? lan=english Hope somebody finds it useful. :) Regards -- Vicente Aguilar <bisente at bisente.com> |

Hi I've recently released the daemontools scripts I use to run both Asterisk and Flash Operator Panel, and a macro to tell whether today is a holiday or not and jump to different dialplan places accordingly. They are here: daemontools scripts: http://www.bisente.com/blog/2007/04/27/spanish-asterisk-y-daemontools-spanishenglish-asterisk-and-daemontools-english/?lan=english is-holiday macro:

Hi, Using syslinux 3.80, I'm seeing pxelinux.bin hanging after the (succesfull) transfer of the default file. Running a lan trace, it appears that all goes fine until the time pxelinux sends a TFTP RRQ for menu.c32 to the TFTP server, gets the first data packet back, and apparently freezes at this point. The TFTP server then times out and retries (3 times) then finally sends an error packet

Good Afternoon, As per the installation guide, section 30.2.2 I?ve created an efidefault file at /var/lib/tftpboot/pxelinux/pxelinux.cfg/efidefault However, this file is never requested by the 64 bit PXE loader (bootx64.efi), as shown by tcpdump: 75 RRQ "/pxelinux/42272635-0011-5053-ACF2-82A100E615F2" octet tsize 0 blksize 512 59 RRQ "/pxelinux/01-00-50-56-A7-BA-BF"

Hello, Can someone outline what tutorials will be covered at this year's AstiCon in AZ? Are the tutorials going to be worthwhile for fellow Asterisk users/admins that have been actively building, running, and administering Asterisk boxes for years? I have a suggestion for one demo that would certainly interest me and other more advanced users. I would *love* to see a hands on live

Hello, I am attempting to setup a PXE setup for a network using multiple subnets. The current layout has dhcp on one subnet (10.16.215.8/30), tftp on another (10.16.194.0/23), and the system to be installed on yet another subnet ( 10.16.233.0/24 [there's actually about 30 different subnets the system to be installed could be on]). When I have the system to be installed on the same subnet as

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

Gene and co, Now my pxelinux efi 64 boot is properly loading syslinux.efi (via TFTP) It then issues a TFTP file request for efi.x64/pxelinux.cfg/ldlinux.e64. (All my efi x64 content is under efi.x64/pxelinux.cfg). However, I see that it fails to properly negotiate the TFTP options with my TFTP server. so it never transfers ldlinux.e64 over. In its file request packet, it asks for these TFTP

Changes with nginx 0.7.66 07 Jun 2010 *) Security: now nginx/Windows ignores default file stream name. Thanks to Jose Antonio Vazquez Gonzalez. *) Change: now the charset filter runs before the SSI filter. *) Change: now no message is written in an error log if a variable is not found by $r->variable() method. *) Change:

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

Hi Guys, i have a problem with PXE/UEFI Boot. Legacy PXE Boot is working fine. I use Dnsmasq with integrated tftp. As Mentioned above, legacy pxe boot is working fine, tcpdump shows: --- start tcpdump legacy pxe boot --- 13:44:16.589197 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from f8:ca:b8:06:7d:ed (oui Unknown), length 548 13:44:20.543910 IP 0.0.0.0.bootpc >