Displaying 20 results from an estimated 6000 matches similar to: "LUA"
2013 Oct 15
23
[PATCH 00/21] Upgrade to Lua 5.2.2, add filesystem module and get_key binding
Hi,
This series targets automatic boot menu generation, but most of it
is the Lua upgrade, because I got tired reading deprecated API docs.
It's mostly a straightforward forward port of the earlier Syslinux
specific changes to Lua 5.1, except that:
* I chose the add a stub getenv() implementation to the COM32 API
instead of #ifdefing out all the references in Lua, and
* I kept oslib
2014 Mar 02
3
pull request: upgrade to Lua 5.2.3, automatic Linux boot menu and cmenu binding
Hi,
Yes, I'm back with this pet peeve of mine again. Most of the old cover
letter at https://gist.github.com/wferi/6989458 still applies; I'd like
to reiterate its last paragraph here, too:
> And an official stat() implementation would be very useful. After
> inventing mine, I noticed rosh also invented its own...
Anyway, here it is:
The following changes since commit
2013 Oct 15
0
Upgrade to Lua 5.2.2, add filesystem module and get_key binding
Op 2013-10-15 om 20:03 schreef Ferenc W?gner:
> Hi,
>
> This series targets automatic boot menu generation, but most of it
> is the Lua upgrade, because I got tired reading deprecated API docs.
> It's mostly a straightforward forward port of the earlier Syslinux
> specific changes to Lua 5.1, except that:
>
> * I chose the add a stub getenv() implementation to the
2014 Jun 03
2
Undef symbol FAIL: luaL_checklstring in vesa.c32
"H. Peter Anvin" <hpa at zytor.com> writes:
> On 06/03/2014 02:59 AM, Ady wrote:
>
>> Testing Syslinux 6.03-pre13 in a BIOS 32-bit VM,
>> boot: vesa.c32
>> Undef symbol FAIL: luaL_checklstring
>> Failed to load COM32 file vesa.c32
>> boot:
>>
>> Is there a Lua-related issue?
>>
>> Is vesa.c32 expecting some kind of
2014 Jun 03
3
Undef symbol FAIL: luaL_checklstring in vesa.c32
Testing Syslinux 6.03-pre13 in a BIOS 32-bit VM,
boot: vesa.c32
Undef symbol FAIL: luaL_checklstring
Failed to load COM32 file vesa.c32
boot:
Is there a Lua-related issue?
Is vesa.c32 expecting some kind of argument?
TIA,
Ady.
2012 Sep 19
1
[PATCH 1/1] lua: Enabling io.read() in Lua.c32 with some restrictions
From: Hung-chi Lihn <hlihn at google.com>
The current Lua.c32 does not enable io.read() due to some missing library
functions. However, this strongly limits the Lua script from getting user
inputs and reading files (even in pxelinux via TFTP).
This patch enables io.read() in Lua.c32 with some restrictions:
1. the io.read("*line") is fully supported.
2. the
2010 Jul 02
1
[syslinux:master] lua: Modernize the Makefile
Op 20100702 om 11:21 schreef syslinux-bot for H. Peter Anvin:
>
> lua: Modernize the Makefile
<bigsnip/>
> -liblua.a: $(LIBLUA_OBJS)
> +$(LIBLUA) : $(LIBLUA_OBJS)
> + rm -f $@
> $(AR) cq $@ $^
> $(RANLIB) $@
FWIW: Today I also found that missing `rm -f $@`
Cheers
Geert Stappers
2013 Aug 30
2
Automatic boot menu?
"H. Peter Anvin" <hpa at zytor.com> writes:
> On 08/29/2013 04:14 AM, Ferenc Wagner wrote:
>
>> "H. Peter Anvin" <hpa at zytor.com> writes:
>>
>>> On 08/22/2013 10:20 AM, Ferenc Wagner wrote:
>>>
>>>> Now that Syslinux has ls.c32 and lua.c32, it should be possible to build
>>>> a customizable boot menu in
2014 Jun 05
1
Undef symbol FAIL: luaL_checklstring in vesa.c32
Ady <ady-sf at hotmail.com> writes:
>> "H. Peter Anvin" <hpa at zytor.com> writes:
>>
>>> I didn't realize how many modules there are in Lua, and quite frankly
>>> not all of them are very well named in the sense that it is clear that
>>> they are Lua-related. vesa.c32 is one of those - it is one of several
>>> Lua
2008 May 27
4
why there is no liblua5.1.so in /usr/lib?
hello all:
I want to install ModSecurity v2.5.4 in my system. I do the following setup to install the lua
tar -xzvf lua-5.1.3.tar.gz
cd lua-5.1.3/src
make linux
cd ..
make install
The ModSecurity ask me to add "LoadFile /usr/lib/liblua5.1.so" to the http.conf,but there is no liblua5.1.so in /usr/lib.
I have search it and i didn't find the solution.
Can any one tell me why
2012 Sep 19
1
[PATCH 1/1] lua: Cleaned up the dmi table structure in Lua.c32 and added all missing DMI subtables
From: Hung-chi Lihn <hlihn at google.com>
In the current Lua.c32 DMI implementation, it is a flat table with dotted
names in table entries. It also misses a number DMI sub-tables.
This patch, cleans up the DMI table structure using Lua's nested table
structure and adds all missing DMI sub-tables. If a DMI sub-table is not
supported by the hardware (not filled), then the corresponding
2016 Apr 21
2
Creating Syslinux UEFI usb boot
On Thu, Apr 21, 2016 at 6:39 AM, Gene Cumm <gene.cumm at gmail.com> wrote:
> On Thu, Apr 21, 2016 at 3:29 AM, Atle Holm <atle at team-holm.net> wrote:
>> Under EFI/BOOT are the following files:
>> BOOTIA32.EFI (from efi32/efi/syslinux.efi)
>> BOOTX64.EFI (from efi64/efi/syslinux.efi)
>> ldlinux.sys (copied from root of partition)
>> lua.c32
>>
2014 Nov 10
1
pxelinux 6.03 lua module not loading syslinux.c32 dmi.c32 etc
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
2014 Nov 28
2
[PATCH] Add ldisk.c32 Lua module
ldisk.c32 is a Lua module that provides information about disks to Lua scripts
The example script com32/lua/test/detect_disks.lua uses it to implement some-
thing akin to 'disk.c32'.
The name 'ldisk.c32' was chosen to avoid a name-clash with 'disk.c32'.
---
com32/lua/src/Makefile | 1 +
com32/lua/src/ldisk.c | 103
2017 Aug 24
4
cmenu.c32 Symbol not found luaL_checklstring
Hello everyone,
I am trying to PXE boot my Acer Aspire G3-773G laptop. It uses UEFI,
so I load 64bit syslinux.efi (v6.03) and it automatically loads
ldlinux.e64. All is fine.
But when I want to use cmenu.c32 (with UI cmenu.c32 in the config file),
the loader downloads:
* cmenu.c32
* libmenu.c32
* libcom32.c32
* libutil.c32
Then syslinux reports: "unable to load cmenu.c32:
2006 May 01
6
[PATCH] Use stddef.h in Mini-OS to define size_t
Please patch Mini-OS so that it uses stddef.h to define size_t and
NULL. This problem fixes errors that occur when linking Mini-OS with
ANSI standard code that uses stddef.h.
John
diff -ur oxen-3.0-testing/extras/mini-os/include/lib.h nxen-3.0-testing/extras/mini-os/include/lib.h
--- oxen-3.0-testing/extras/mini-os/include/lib.h 2006-04-14 22:21:55.000000000 -0400
+++
2014 Aug 24
1
Library_modules (list of & wiki write permissions)
Hello,
I poked a little bit to extract the list of modules dependencies in
Syslinux v6 (see below). I have attached a bash script that generate a
nice table from the tarball. The output can either be an ASCII table, or
wiki markup, typically for the page Library_modules[1].
I am not in the wiki Editor group, so I can't put that in the wiki.
anyway, here's an updated dependency tree for
2009 Aug 29
2
Asterisk 1.6.0.14 and 1.6.1.5 Now Available
The Asterisk Development Team is pleased to announce the release of Asterisk
1.6.0.14 and 1.6.1.5. Asterisk 1.6.0.14 and 1.6.1.5 are available for immediate
download at http://downloads.asterisk.org/pub/telephony/asterisk/
Asterisk 1.6.0.14 is the first full, non-security release since 1.6.0.10.
The release candidate 1.6.0.11-rc1 was redone as 1.6.0.14-rc1 (which this
release has been created
2009 Aug 29
2
Asterisk 1.6.0.14 and 1.6.1.5 Now Available
The Asterisk Development Team is pleased to announce the release of Asterisk
1.6.0.14 and 1.6.1.5. Asterisk 1.6.0.14 and 1.6.1.5 are available for immediate
download at http://downloads.asterisk.org/pub/telephony/asterisk/
Asterisk 1.6.0.14 is the first full, non-security release since 1.6.0.10.
The release candidate 1.6.0.11-rc1 was redone as 1.6.0.14-rc1 (which this
release has been created
2011 Oct 04
1
Added DHCPINFO Tables to the lua.c32 Implementation - syslinux-4.04
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