similar to: keystrokes

On Sat, Sep 6, 2014 at 8:18 AM, Ady <ady-sf at hotmail.com> wrote: > Hello Syslinux Team, > > What actions are _supposed_ to be triggered by each of: > > [Ctrl-J] > [Ctrl-M] > > in the Syslinux command line in version 6.03-pre20? They should do nothing special but either might be interpreted like an <enter>. > Are there any differences between CLI and

> On Sat, Sep 6, 2014 at 8:18 AM, Ady <ady-sf at hotmail.com> wrote: > > Hello Syslinux Team, > > > > What actions are _supposed_ to be triggered by each of: > > > > [Ctrl-J] > > [Ctrl-M] > > > > in the Syslinux command line in version 6.03-pre20? > > They should do nothing special but either might be interpreted like an

> Ady <ady-sf at hotmail.com> writes: > > >> On Sat, Sep 6, 2014 at 8:18 AM, Ady <ady-sf at hotmail.com> wrote: > >> > >>> What actions are _supposed_ to be triggered by each of: > >>> > >>> [Ctrl-J] > >>> [Ctrl-M] > >>> > >>> in the Syslinux command line in version 6.03-pre20? >

Ady <ady-sf at hotmail.com> writes: >> On Sat, Sep 6, 2014 at 8:18 AM, Ady <ady-sf at hotmail.com> wrote: >> >>> What actions are _supposed_ to be triggered by each of: >>> >>> [Ctrl-J] >>> [Ctrl-M] >>> >>> in the Syslinux command line in version 6.03-pre20? >> >> They should do nothing special but

Ady <ady-sf at hotmail.com> writes: >> Ady <ady-sf at hotmail.com> writes: >> >>>> On Sat, Sep 6, 2014 at 8:18 AM, Ady <ady-sf at hotmail.com> wrote: >>>> >>>>> What actions are _supposed_ to be triggered by each of: >>>>> >>>>> [Ctrl-J] >>>>> [Ctrl-M] >>>>>

Hello Ady, On 27.08.2014 16:46, Ady wrote: >> On 01.08.2014 19:22, Ady wrote:>> On 24.07.2014 17:32, Gene Cumm wrote: >>>>> On Thu, Jul 24, 2014 at 10:29 AM, Philipp Hahn <hahn at univention.de> >> wrote: >>>>>> On 24.07.2014 13:52, Gene Cumm wrote: >> ... >>>>>> Your special build gets the gateway working, but the

> Hello, > > On 01.08.2014 19:22, Ady wrote:>> On 24.07.2014 17:32, Gene Cumm wrote: > >>> On Thu, Jul 24, 2014 at 10:29 AM, Philipp Hahn <hahn at univention.de> > wrote: > >>>> On 24.07.2014 13:52, Gene Cumm wrote: > ... > >>>> Your special build gets the gateway working, but the downloaded InitRD > >>>> still

On Thu, Sep 11, 2014 at 4:09 PM, Ady <ady-sf at hotmail.com> wrote: >> Since keystrokes were brought up, this seems like a reasonable time to >> make the following seemingly simple-to-implement feature request: >> >> Navigating a multi-level menu structure seems to require use of >> UP/DOWN/ENTER/ESC. It would be easier to quickly search/navigate if it >>

Hello, On 01.08.2014 19:22, Ady wrote:>> On 24.07.2014 17:32, Gene Cumm wrote: >>> On Thu, Jul 24, 2014 at 10:29 AM, Philipp Hahn <hahn at univention.de> wrote: >>>> On 24.07.2014 13:52, Gene Cumm wrote: ... >>>> Your special build gets the gateway working, but the downloaded InitRD >>>> still gets corrupted sometimes. Boot-time is down

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.

On 8/4/17, Ady Ady via Syslinux <syslinux at zytor.com> wrote: > >> Note, I am using syslinux from Ubuntu 16.04.2, presume that is 6.03. >> >> Regards, >> Barry > > Before investing time in replying to each different (unexpected) > behavior, I would suggest testing with *pre-built* binaries from > 6.04-pre1 downloaded from kernel.org (considering the

Hi everyone, I have released Syslinux 6.03. It is by and large identical to 6.03-pre20. I would like to do a short cycle for 6.04, because 64-bit support for ext4 has come up as a very high priority. Therefore I do not want to stuff too many things into the 6.04 release but hold them for 6.05. Thanks to Ady for most of the changelog. Changes in 6.03: * chain: Fix chainloading on 6.02

The following are new Lua c32 modules in 6.03-pre*: cmenu.c32: cpu.c32: dhcp.c32: dmi.c32: lfs.c32: pci.c32: syslinux.c32: vesa.c32: I am wondering whether the following modules, which are _not_ new and are also included in 6.03-pre*, have _any_ relation either to the above list or to Lua: cpuid.c32: cpuidtest.c32: dmitest.c32: pcitest.c32: vesainfo.c32: TIA, Ady.

On Sat, Sep 13, 2014 at 11:34 AM, Ady <ady-sf at hotmail.com> wrote: > >> On Thu, Sep 11, 2014 at 4:09 PM, Ady <ady-sf at hotmail.com> wrote: >> >> >> Since keystrokes were brought up, this seems like a reasonable time to >> >> make the following seemingly simple-to-implement feature request: >> >> >> >> Navigating a

Since keystrokes were brought up, this seems like a reasonable time to make the following seemingly simple-to-implement feature request: Navigating a multi-level menu structure seems to require use of UP/DOWN/ENTER/ESC. It would be easier to quickly search/navigate if it could be done with fingers stationed on the arrow keys so that the eyes can stay focused on the screen. Current

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

> On Thu, Sep 11, 2014 at 4:09 PM, Ady <ady-sf at hotmail.com> wrote: > > >> Since keystrokes were brought up, this seems like a reasonable time to > >> make the following seemingly simple-to-implement feature request: > >> > >> Navigating a multi-level menu structure seems to require use of > >> UP/DOWN/ENTER/ESC. It would be easier to

"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

Hi, the current 6.03~pre20 works great, can you please "finally" release this as 6.03? time is running out for Debian and I'd really like to avoid putting 6.03~pre20 labeled as such in Debian 8 (jessie). Regards, Daniel

Hi, HPA: Thanks for the nice new features, appreciate that. Syslinux is always a nice program. For the new version, 3.10-pre20, I encountered a problem now, my client machine uses sis900 chip, and it still can not run simple menu with pxelinux in this version (3.10-pre20). It's same situation as I encountered when I used syslinux 3.07, 3.08 and 3.09. For 3.10-pre20, I compiled in Fedora