similar to: [menu] Bug: 'cm' is used before it is initialized

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

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

I have a menu conf as follows: LABEL enabled, use as item LABEL disabled, use as description SEPARATOR LABEL enabled, use as item LABEL disabled, use as description In this situation, I expect the cursors to be able to select from only the two enabled lines. However, the final disabled line is also selectable. Even if I put a final separator and/or disabled label the final line of the menu

The behaviour of the menu system is odd when an empty / not existing config file is specified: the screen is cleared but not even the menu frame is displayed. It seems to be a problem with run_menu() from menumain.c: if (top != prev_top) { draw_menu(entry, top, 1); display_help(me->helptext); } else if (entry != prev_entry) {

This patch modifies the simple menu com32 program to include integrated load progress. It also adds new options to the simple menu configuration MENU LOADMSG -- allows the user to specify the text to display when loading MENU LOADMSGROW -- controls where the text is written Example configuration: MENU LOADMSG Booting MENU LOADMSGROW 25 It works with my setup, please let me know if you find

Hi, We are using pxelinux at my company to test our product. And there are limitations that we have hit in the past w.r.t. the max length of a path, or the max length of a module name (in mboot.c / mboot.c32). We've used workarounds in the past, and reorganized the directory structure, but we face that problem again. Out of the 128 / FILENAME_MAX chars that can be used, 110 - 120 go to the

From: Matt Fleming <matt.fleming at linux.intel.com> This is a series of patches that, * shrink the core by moving things into an ldlinux ELF module * begin wiring up some of the C versions of various functions The core now only contains essential code and loads the ldlinux module to do everything else, like providing a command line interface and loading kernels. The config file parsing

Hello, I'm using iPXE to chain to menu.c32, here is the boot script: #!ipxe dhcp chain http://my-site/menu.c32 http://my-site/boot.php After ipxe promote "http://my-site/menu.c32...... ok", the machine hangs. Then I try to figure out where it does stop. First I put a printf() statement in In syslinux/com32/menu/menumain.c:main:, right after start_console(), then boot

The menu system allows one to specify an alternative config file and it's also possible to specify more than one file. menu.txt got "If you specify more than one file, they will all be read, in the order specified." What is the desired failure mode if one of those files doesn't exist? com32/menu/menumain.c calls parse_configs() which itself calls parse_one_config

Hello, While experimenting with possible menu layout found this issue; the entry for MENU BEGIN doesn't follow MENU INDENT. *Sample config* label - menu disable menu label Distro label rhel menu indent 2 menu label RHEL label cent menu indent 2 menu label Centos label fed menu indent 2 menu label Fedora menu begin menu indent 2 menu label Others menu end # 'Others'

> Hello, > > Here's a small enhancement feature for menu.c32. Looking for feedback before > starting any coding (not sure when I'll have time for implementation) > > Regards, > Dany St-Amant > > > *Problem statement* > > When MENU HIDDEN is used on an headless server, any noise on the serial > console can interrupt the boot; it would be

On Sat, Nov 22, 2014 at 10:39 AM, Martin Str|mberg <ams at ludd.ltu.se> wrote: > Hello. > > Use the z size specifier to printf-ing size_t variables to get rid of gcc > warning > format ?%08x? expects type ?unsigned int?, but argument 2 has type ?long unsigned int? Please, add the signed-off line. > > > -- > MartinS > > diff --git

Hello. Use the z size specifier to printf-ing size_t variables to get rid of gcc warning format ?%08x? expects type ?unsigned int?, but argument 2 has type ?long unsigned int? -- MartinS diff --git a/com32/lib/syslinux/initramfs_file.c b/com32/lib/syslinux/initramfs_file.c index 7eb55b5..9f9fa75 100644 --- a/com32/lib/syslinux/initramfs_file.c +++ b/com32/lib/syslinux/initramfs_file.c @@

Hi, I have a LDAP backend for my Samba 3.0.2, and everything seems to work except adding XP machines to the domain, and unix logins with a ldap client. Since this mail is very long, I have created a small index, so you don't get exhaustet in the middle of all the logs... ;) 1. LDAP user-creation 2. Group info 3. pam/nss info 4. smb.conf [global] 5. Log from trying to add machine to

Add functions implementing MSI-X support. First user will be virtio-pci. Note that platform must set a flag to declare MSI supported. For PC this will be set by APIC. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- Makefile.target | 2 +- hw/msix.c | 423 +++++++++++++++++++++++++++++++++++++++++++++++++++++++ hw/msix.h | 35 +++++ hw/pci.h | 20 +++ 4

Add functions implementing MSI-X support. First user will be virtio-pci. Note that platform must set a flag to declare MSI supported. For PC this will be set by APIC. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- Makefile.target | 2 +- hw/msix.c | 423 +++++++++++++++++++++++++++++++++++++++++++++++++++++++ hw/msix.h | 35 +++++ hw/pci.h | 20 +++ 4

Add functions implementing MSI-X support. First user will be virtio-pci. Note that platform must set a flag to declare MSI supported: this is a safety measure to avoid breaking platforms which should support MSI-X but currently lack this in the interrupt controller emulation. For PC this will be set by APIC. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- Makefile.target | 2

Add functions implementing MSI-X support. First user will be virtio-pci. Note that platform must set a flag to declare MSI supported: this is a safety measure to avoid breaking platforms which should support MSI-X but currently lack this in the interrupt controller emulation. For PC this will be set by APIC. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- Makefile.target | 2

Add functions implementing MSI-X support. First user will be virtio-pci. Note that platform must set a flag to declare MSI supported: this is a safety measure to avoid breaking platforms which should support MSI-X but currently lack this in the interrupt controller emulation. For PC this will be set by APIC. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- Makefile.target | 2

Add functions implementing MSI-X support. First user will be virtio-pci. Note that platform must set a flag to declare MSI supported: this is a safety measure to avoid breaking platforms which should support MSI-X but currently lack this in the interrupt controller emulation. For PC this will be set by APIC. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- Makefile.target | 2