Displaying 20 results from an estimated 600 matches similar to: "Patch: Readconfig wont parse certain options anymore"
2019 Jul 09
0
[PATCH] core: Add support for BLS Type 1 entries
Modern distributions are moving toward a common boot scheme called "The Boot
Loader Specification". This patch enables syslinux to parse the drop-in files
that are defined by this new specification.
Link to documentation of the options added to syslinux by this patch:
https://drive.google.com/uc?export=download&id=1nuRISVJeE1whYggFURywoQFpPzc6s1MC
MD5 (syslinux-bls1.txt) =
2010 May 30
1
[RFC PATCH] menu: support single key booting
If MENU COMMIT is specified for a label, execute it automatically
when its hotkey is pressed.
Signed-off-by: Ferenc Wagner <wferi at niif.hu>
---
com32/menu/menu.h | 1 +
com32/menu/menumain.c | 10 ++++++++--
com32/menu/readconfig.c | 6 +++++-
3 files changed, 14 insertions(+), 3 deletions(-)
As mentioned on IRC, people ask for this.
So here's something to talk
2019 May 24
3
[PATCH] (vesa)menu.c32: Add support for BLS
Modern distributions are moving toward a common boot scheme called "The Boot
Loader Specification". This patch enables syslinux's (vesa)menu.c32 modules to
parse the drop-in files that are defined by this new specification.
Link to The Boot Loader Specification:
https://systemd.io/BOOT_LOADER_SPECIFICATION
Link to demonstration bootdisk image (82MB gzipped):
2019 May 27
0
[PATCH] (vesa)menu.c32: Add support for BLS
Gregory Bartholomew wrote:
> On Sat, May 25, 2019 at 3:42 PM Sebastian Herbszt <herbszt at gmx.de>
> wrote:
> >
> > Gregory Lee Bartholomew wrote:
> > > Modern distributions are moving toward a common boot scheme called
> > > "The Boot Loader Specification".
> >
> > Which distributions are using this yet?
[copy & paste from other
2016 Jun 29
0
Fwd: [PATCH] {vesa}menu.c32 feature => hide menu entry for specific sources
good afternoon.
As promised to Mr Cumm few weeks before, I forward you the mail that I had wrongly sent directly to Mr Anvin.
This is something I've done for my company usage and I submit it to you. Feel free to include it if you think this can be usefull for others ..
Context:
In my company, we have several distinct PXE server (depending on the location: europe, asia, ....). each of these
2013 Jun 12
0
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
>From f48d79be8c79241dd4635165e393683809edd823 Mon Sep 17 00:00:00 2001
From: Matt Fleming <matt.fleming at intel.com>
Date: Wed, 12 Jun 2013 13:04:44 +0100
Subject: [PATCH] PATH: Change the PATH directive syntax
In retrospect, choosing the colon character as the entry separator for
the PATH directive was not a smart move, as that character is also used
in TFTP-style paths. This conflict
2013 Jun 12
0
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
On 06/12/2013 09:40 AM, Matt Fleming wrote:
> On Tue, 11 Jun, at 03:54:21AM, H. Peter Anvin wrote:
>> On 06/11/2013 01:03 AM, Matt Fleming wrote:
>>> On Mon, 10 Jun, at 07:57:50AM, H. Peter Anvin wrote:
>>>> Either that or make the path a list rather than a string, using the
>>>> normal word separators when entered on the command line, a bit like the
2005 Mar 07
0
gcc4 warnings
Below is a patch to get rid of several warnings which occur while
building syslinux 3.07 with the current gcc 4 snapshot. This fixes all
the warnings except one unused variable.
Take them or leave them as you see fit. They're all com32 stuff that's
pulled in from external sources.
--- syslinux-3.07/memdisk/unzip.c.gcc4 2004-12-07 23:29:22.000000000 -0500
+++
2013 Jun 12
5
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
On Tue, 11 Jun, at 03:54:21AM, H. Peter Anvin wrote:
> On 06/11/2013 01:03 AM, Matt Fleming wrote:
> > On Mon, 10 Jun, at 07:57:50AM, H. Peter Anvin wrote:
> >> Either that or make the path a list rather than a string, using the
> >> normal word separators when entered on the command line, a bit like the
> >> (t)csh does. That is a bigger change but is probably
2019 May 25
2
[PATCH] (vesa)menu.c32: Add support for BLS
On Sat, May 25, 2019 at 3:42 PM Sebastian Herbszt <herbszt at gmx.de> wrote:
>
> Gregory Lee Bartholomew wrote:
> > Modern distributions are moving toward a common boot scheme called
> > "The Boot Loader Specification".
>
> Which distributions are using this yet?
>
> > This patch enables syslinux's
> > (vesa)menu.c32 modules to parse the
2013 Jun 24
2
[bug] Syslinux-5.11-pre2: IPAPPEND/SYSAPPEND inconsistent base
core and the simple menu do not interpret the IPAPPEND/SYSAPPEND
directives in the same way. Which is the proper way? Either way,
this should be clarified in the documentation.
com32/elflink/ldlinux/readconfig.c:
} else if ((ep = looking_at(p, "ipappend")) ||
(ep = looking_at(p, "sysappend"))) {
uint32_t s = strtoul(skipspace(ep), NULL,
2012 May 04
3
[GIT PULL] elflink fixes
Peter,
Paulo reported some problems with his config files under ISOLINUX and
PXELINUX - basically TIMEOUT and TOTALTIMEOUT were broken. The patches
I've pushed to the elflink branch fix this and also fix parsing of the
ALLOWOPTIONS config directive.
The following changes since commit d5e02fb16a11bfdbce1e90a39e6cb5f2ad925389:
get_key: Valid key values are positive (2012-04-17 11:25:53
2013 Jun 24
2
[bug] Syslinux-5.11-pre2: IPAPPEND/SYSAPPEND inconsistent base
On Sun, Jun 23, 2013 at 11:09 PM, Gene Cumm <gene.cumm at gmail.com> wrote:
> On Sun, Jun 23, 2013 at 11:06 PM, Gene Cumm <gene.cumm at gmail.com> wrote:
>> core and the simple menu do not interpret the IPAPPEND/SYSAPPEND
>> directives in the same way. Which is the proper way? Either way,
>> this should be clarified in the documentation.
>
> To be clear:
2012 Apr 17
2
[GIT PULL] elflink warning fixes and auto extension support
Hi,
I just pushed out changes that fix pretty much all the compiler build
warnings on the elflink branch. Also, I've added "auto extension"
support so that if the user doesn't type the file name extension it will
automatically be looked up, e.g. now typing "ls" will execute "ls.c32".
The following changes since commit
2019 May 25
0
[PATCH] (vesa)menu.c32: Add support for BLS
Gregory Lee Bartholomew wrote:
> Modern distributions are moving toward a common boot scheme called
> "The Boot Loader Specification".
Which distributions are using this yet?
> This patch enables syslinux's
> (vesa)menu.c32 modules to parse the drop-in files that are defined by
> this new specification.
Any reason why you don't try to implement this in syslinux
2013 Jun 24
0
[bug] Syslinux-5.11-pre2: IPAPPEND/SYSAPPEND inconsistent base
On Sun, Jun 23, 2013 at 11:06 PM, Gene Cumm <gene.cumm at gmail.com> wrote:
> core and the simple menu do not interpret the IPAPPEND/SYSAPPEND
> directives in the same way. Which is the proper way? Either way,
> this should be clarified in the documentation.
To be clear: core treats the value as always hexidecimal while simple
menu treats it as decimal unless a 0x prefix is
2011 May 25
1
[GIT PULL] elflink ldlinux
Hi,
These patches contain support for some features that are already in
Syslinux 4 but weren't working properly on the elflink branch. It's
another step closer to feature parity with Syslinux 4.
Having to jump through the comboot API for localboot support is less
than ideal and I'll eventually fix that, probably when we move a big
chunk of code from asm to C.
Also, there's a
2007 Mar 15
1
my_isspace can be isblank
Hey,
I noticed my_isspace() is being used in menu/mainmenu and readconfig
com32 modules.
Why not use isblank() instead? Here's a patch:
thanks.
Ram
--- com32/modules/menu.h
//depot/opensource/main/syslinux-3/com32/modules/menu.h#2
+++ com32/modules/menu.h 07-03-15 16:27:14
@@ -87,11 +87,6 @@
void parse_configs(char **argv);
extern int (*draw_background)(const char *filename);
-static
2013 Jun 24
2
[5.11-pre1] SYSAPPEND does not work (IPAPPEND alias works)
On Sun, Jun 23, 2013 at 3:16 PM, Gerardo Exequiel Pozzi
<vmlinuz386 at yahoo.com.ar> wrote:
> I guess the bug is here (com32/menu/readconfig.c)
>
> 910 } else if (looking_at(p, "ipappend") || looking_at(p,
> "sysappend")) {
> 911 if (ld.label)
> 912 ld.ipappend = atoi(skipspace(p + 8));
> 913
2016 Apr 27
2
PXERETRY directive
On Wed, Apr 27, 2016 at 06:23:38AM -0400, Gene Cumm via Syslinux wrote:
> On Thu, Apr 21, 2016 at 10:30 PM, Ady via Syslinux <syslinux at zytor.com> wrote:
> > Would someone please be so kind to explain / describe the PXERETRY
> > directive?
>
> $ git grep -ni pxeretry
-i ignore case ("thanks" said the person who exact case matching search )
>