similar to: LUA scripting in syslinux

Hi, Probably too late for the main tracks, but it would be nice to see a syslinux-related presentation at FOSDEM 2012. There are a few tracks where syslinux fits in (Configuration and Systems Management, Embedded, Distribution ?) so it shouldn't be hard to get one or more slots. I enjoyed Peter's presence two years ago and it lead to an uptake of the project (I remember Erwan

Hi, As a packager of syslinux, I would like to get rid of the dependency of syslinux on Crypt::PasswdMD5, as it does not ship with RHEL/CentOS by default and therefor is an additional hurdle for people on those distributions to use a more recent syslinux. (I am also involved with the Rear project that relies on a more recent syslinux, and in various corporate environments need a recent

Hi, I have been experimenting a bit with lua.c32 and I have created a small lua.c32 wiki page at: http://syslinux.zytor.com/wiki/index.php/Lua.c32 With my minimal knowledge about Lua (and the inconvenience of not being able to copy&paste or edit scripts) I discovered that the dmi module has 2 functions (supported, gettable) and a syslinux module with 1 function (run_command). Do we

Hi, I couldn't find any definitive answers from the documentation. Although older posts on this list were negative, it was supposedly not very difficult to implement and considered for syslinyx 4. So does multi serial support now work in syslinux 4 today ? If not, what does syslinux do if more than one serial directive is used in the configuration ? Use the last one listed ? Thanks in

Hi, This must be a FAQ somewhere, although I am unable to find the answer quickly. We would like to have a bootable USB device offer the possibility to boot from the local disk. Unfortunately what happens when using 'chain.c32 hd1' is that GRUB works, but the GRUB configuration refers to it's disk as 'hd0', so booting an entry fails. One has to manually change 'root

On Mon, 24 Jun 2013, Matt Fleming wrote: > On Mon, 24 Jun, at 10:27:52AM, Thomas B?chler wrote: > >> As far as I can see, this is an issue of the BIOS firmware not handling >> things at all - there is not even a code path to the function that boots >> Linux via BIOS. I can only guess that this is a result of a failed merge >> followed by not testing 6.00 on BIOS

On Wed, 26 Jun 2013, Helmut Hullen wrote: > Du meintest am 25.06.13: > >>> We could probably fabricate a script of some sort to check for the >>> required version of gnu-efi, and skip it if not found, unless the >>> user explicitly requested that the EFI files be built, in which case >>> we'd error out. >>> >>> Thoughts? >

Hi, I would be very interested in a possibility to create variables or macros within syslinux. One of the things I would like to have is a way to query DMI/VPD information, and use that as kernel parameters or to influence eg menu's or boot labels (based on system information). One of those very specific needs is to get the MAC address of the first onboard interface (which is available

Hi, Since a --direct-io feature was requested a few times the past decade with little response and the actual patch is quite trivial, I patched both v3.0.9 and master branch and included the patches here. If this functionality is acceptable I don't mind spending the additional effort to update the documentation, etc. Beware that the underlying filesystem needs Direct I/O support,

Hi, I am looking for a solution (that apparently is similar to how the Windows installation process works) where the isolinux bootloader would act different when there is no MBR on the first disk, or when there is one. This is useful for instance when there is no MBR (and thus no OS) on the system to automatically show a menu (or even start the installation). But When there is an MBR on the

I'm trying to get this bit of code to work with the lua.c32 interpreter: --- sample, the goal is to build a script that will allow me to enter a 4digit mt and load the bios iso accordingly print ("enter machine type :") mt = io.read() print ("you entered...",mt) doStuff() if (mt == "8141") then syslinux.run_command("memdisk

Previous-Subject: constants and line continuation Op 20100713 om 16:21 schreef Dag Wieers: > On Tue, 13 Jul 2010, Jim Cromie wrote: >> On Fri, Jul 9, 2010 at 3:22 PM, H. Peter Anvin <hpa at zytor.com> wrote: >>> On 07/09/2010 12:40 PM, Warren Block wrote: >>>> If these are FAQ entries, sorry, I searched but did not find. >>>> Maybe the wrong terms.

Hello, For Lua inclusion in Syslinux an idea to ship with an com32/lua/assist directory and an com32/lua/patches directory. In the patches directory patches against a pristine lua tarball and the assist dir contains scripts for further tayloring. This is what I have in mind: | milleune at inertia:~ | $ git clone http://www.stappers.it/tracking/syslinux/.git syslinux-lua-stappers | milleune at

I would like to announce the availability of llvm-lua. llvm-lua, converts Lua bytecode to LLVM IR code and supports JIT and static compiling. Using LLVM gives Lua JIT support on cpu architectures other then x86. I converted the Lua bytecode dispatch loop code into a set of C functions one for each opcode. The opcode functions take two parmeters one is the current Lua function's state,

On Mon, Oct 13, 2014 at 12:53:43PM +0200, Ferenc Wagner wrote: > The following changes since commit 81ad566f155fac31089fde69c87059b217e7e9b6: > > NEWS: Update for 6.03 release (2014-10-06 09:27:44 -0700) > > are available in the git repository at: > > https://github.com/wferi/syslinux/ pub > > for you to fetch changes up to

Since Syslinux 4.01-pre2, lua is the master branch. This lua.c32 moudule doesn't support much. There is a much recent lua.c32, made by Marcel Ritter's: http://syslinux.zytor.com/archives/2009-October/013383.html The last time he wrote about the state of his lua branch: ============================================================ The current state is: - VESA: - switching to vesa mode

>>> Erwan <erwan at seanodes.com> schrieb am 10/19/2009 um 10:11 PM in Nachricht <4ADCC807.6090700 at seanodes.com>: > Hey Marcel, Hi Erwan, > I'm in the process to test your lua branch. > I was wondering what is the current state of it. You can pull the current state from here: git pull git://linux.rrze.uni-erlangen.de/syslinux.git luaext The current

On 11/20/16 00:13, Ferenc W?gner via Syslinux wrote: > > This indeed copies the data from the syslinux_file structure (which is > an opaque SYSLINUX_FILE object on the Lua side) into an (interned) Lua > string to make it available to the Lua string functions. > > You probably ask why we copy the data when we create those SYSLINUX_FILE > userdata objects. We don't, the

The following changes since commit 81ad566f155fac31089fde69c87059b217e7e9b6: NEWS: Update for 6.03 release (2014-10-06 09:27:44 -0700) are available in the git repository at: https://github.com/wferi/syslinux/ pub for you to fetch changes up to 68cb978ab7e692d772e4d62d3585b8f7bac43b4b: lua: simplify the function/value handling in the automenu test (2014-10-13 12:44:15 +0200)

Making progress :) I'll document some obtracles I found, to make it easier for the next one implementing push with Dovecot and Lua. First I tried with my usual Alpine based container, but Alpine seems not to build the Lua stuff for Dovecot :( So I moved to an Ubuntu 18.04 based container and the official Dovecot CE repo: FROM ubuntu:18.04 RUN apt-get update && \ apt-get install