similar to: PXELINUX Lua bindings for DHCP in future release?

I have never tried submitting a patch for anything previously, didn't know how to go about it with this particular software project (since the website has been down) and know little to nothing about git since I am stuck in a ClearCase world with work. Please find the previous patch, as an attachment. Sorry it is against 4.04, I have had no specific reason to update but it should still work.

For me the motivation for gpxelinux.0 was the HTTP support. If this would work reliably in newer versions then I could happily live without a iPXE-based pxelinux. On 9 October 2013 13:36, Ferenc Wagner <wferi at niif.hu> wrote: > "H. Peter Anvin" <hpa at zytor.com> writes: > > > The gPXE in the Syslinux tree is ridiculously old. We could either > >

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.

Greetings All. We wanted to be able to parse the DHCP values and options and write a lua script based on the information found. We are also using the CPU flags, but thankfully in at least version 4.04 there is already some CPU value parsing even if it isn't documented. Using the information from the CPU table we wanted to be able to choose the kernel to boot. Using the DHCP table

On Thu, Sep 24, 2015 at 07:57:47AM -0600, Alan Sparks via Syslinux wrote: > On 9/24/2015 4:59 AM, Gene Cumm wrote: > > On Thu, Sep 24, 2015 at 6:33 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > > > >> Now I have something I can reproduce. Booting my same ipxe.iso to > >> perform an initial TFTP load shows what I saw already. Attempting to > >>

Am 06.06.2013 07:00, schrieb Gene Cumm: > iPXE details. My testing was with an Intel PXE OROM in a VMware > hosted platform with 0 issues. > >> 1370470692 192.168.0.90 "GET /arch/boot/syslinux/pxelinux.0" 200 26813 >> "" "iPXE/1.0.0+ (09c5)" This is the iPXE version that comes bundled with qemu as the default qemu boot rom. -------------- next

If this is asked before, please point me at the answer, can't find it... With pxelinux 3.8.6 (or, < 5.x), I was able to chain boot pxelinux.0 from ipxe, having set appropriate values for DHCP options 210 and 209 for the remote file path and the config file. This doesn't work with 6.0.3. With 6.0.3, this throws the "failed to load ldconfig.c32" error now. The files are in

On Thu, Sep 24, 2015 at 6:33 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > Now I have something I can reproduce. Booting my same ipxe.iso to > perform an initial TFTP load shows what I saw already. Attempting to > load a file via http results in an immediate error message with no > resulting traffic as far as I can see. OK. Found it. core/fs/pxe/pxe.h disabled all of the

I'm running pxelinux configured to use the path /bios on the tftp server for all the comboot files. The problem is dmi,syslinux,vesa etc modules are not being loaded in lua. Syslinux.version() returns not found in global index as does dmi.supported() For k,v in pairs(package.loaded) do print (k,v) end; shows that these modules that are normally loaded by lua are not loading. I got an idea

On Sat, Sep 30, 2017 at 08:53:09PM -0400, Gene Cumm wrote: > On Sep 30, 2017 8:47 PM, Bruce Ferrell wrote: > > > > I've recently seen something to the effect that the pxelinux.0 boot loader > > has some limit of 45MB. Is this correct or some misunderstanding? > > No, I've loaded 90MB files. The catch is often TFTP block number rollover. My first thought was:

Hello. I played with UEFI PXE booting the other day, and as usual, used qemu/kvm virtual machine for initial testing/debugging, because it is way easier and faster for this task than using a real hardware. However, it looks like either qemu or {pxe,sys}linux 6.03 is buggy, -- the two does not play well together. When booting, the system successfully loads syslinux.efi, at least the tftp server

On 9/22/2015 4:33 AM, Gene Cumm wrote: > > https://sites.google.com/site/genecsyslinux/sl604p0g15-bios.tgz?attredirects=0&d=1 > https://sites.google.com/site/genecsyslinux/sl604p0g15-x64.tgz?attredirects=0&d=1 > Tried these new binaries this morning. No change, still will not attempt to load ldlinux.c32. As a context, what I'm really trying to do is get a newer

On 9/23/2015 2:08 PM, Ady via Syslinux wrote: > Even if it still hangs with this test, does it hang exactly as before > (i.e. shows only one character and hangs immediately)? It happens with one entry, or two entries, or three. The configuration works otherwise perfectly on any other environment. If I simplify to the the following, it still hangs after outputting the one visible

On 9/23/2015 12:14 AM, Ady via Syslinux wrote: > About your customers' setup... > Are they using official binaries downloaded from kernel.org? Yes. Stock versions, no local modifications. > Which exact version of Syslinux are they using? I've tried versions 3.86, 4.07, 6.01, 6.03. We can only generally use 4.07 or less because of the described ipxe compatibility issues, 6.0x

Hello SYSLINUX folks, thanks for all your hard work over the years! I'm working on a fairly complex deployment services project, and one of the aspects of it is to make it possible to federate deployment services across our university. Supporting existing deployment services is a priority, so I am presently trying to integrate an existing PXELINUX install, part of a FOG windows imaging

On 9/23/2015 3:32 PM, Ady via Syslinux wrote: > >> On 9/23/2015 2:08 PM, Ady via Syslinux wrote: >> >>> Even if it still hangs with this test, does it hang exactly as before >>> (i.e. shows only one character and hangs immediately)? >> >> It happens with one entry, or two entries, or three. >> The configuration works otherwise perfectly on any

Hi, I finally managed to test pxelinux 4.10 pre17 in our VMware environment and can report that HTTP booting seems to work reliably now. Downloads are fairly fast. As a side note, rosh "ls" and "pwd" commands now work as expected with a HTTP TFTP prefix, cool! I'll leave it in production use now and report about any further issues. Can you already tell when a 4.10

On 9/24/2015 4:33 AM, Gene Cumm wrote: > On Wed, Sep 23, 2015 at 5:43 PM, Alan Sparks via Syslinux > <syslinux at zytor.com> wrote: > Although it means another round of testing, you could also consider > lpxelinux.0 which can support HTTP URLs on its own and probably > interacts differently with iPXE. I am curious about a quantifiable > description of "an odd

I seem to be having trouble getting the NFS root filesystem to mount after the kernel boots. As per thread from 2002 16 January (http://www.zytor.com/pipermail/syslinux/2002-January/000028.html), I double checked my DHCP config files, but to no avail. It cannot seem to attach to the mountd port on the bootserver. Here is some output from the kernel: loop: loaded (max 8 devices) Intel(R) PRO/1000

On 9/21/2015 5:44 PM, Gene Cumm wrote: > On Mon, Sep 21, 2015 at 6:23 PM, Alan Sparks via Syslinux >> With pxelinux 3.8.6 (or, < 5.x), I was able to chain boot pxelinux.0 >> from ipxe, having set appropriate values for DHCP options 210 and 209 >> for the remote file path and the config file. This doesn't work with 6.0.3. > > I thought I recall a newer commit