similar to: Final line of menu selectable even if it is disabled

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

Op 2013-12-30 om 14:03 schreef syslinux-bot for Ruben Kerkhof: > Commit-ID: 54b29b18c684f865d81360764d2623bb06fe1d7a > Gitweb: http://www.syslinux.org/commit/54b29b18c684f865d81360764d2623bb06fe1d7a Visiting that URL yields 'Bad commit reference' but that is not the main reason for this e-mail. > Author: Ruben Kerkhof <ruben at rubenkerkhof.com> > AuthorDate:

Another week, *another* -pre. I'm really planning on this being the last one. The shortlog is appended below. Apart from a better fix for the "disabled menu entry" bug it's only documentation updates. Testing from the last -pre's has been pretty quiet, so as soon as Ady and Matt have tested this one and confirmed that the disabled entry bug is finally gone I'll do the

Folks, I've just pushed out another prerelease for the 5.00 branch. The idea behind this -pre was to merge in the final 4.06 release. I'm aiming for a final 5.00 release next week, but as we saw with the 4.06 branch, anything can happen and these deadlines can get pushed backwards. Please, test if you can. One thing that is going to happen next week is a Syslinux-6.00-pre1, which will

On Thu, Jan 01, 2015 at 09:48:16AM -0500, Gene Cumm wrote: > On Thu, Jan 1, 2015 at 7:13 AM, Geert Stappers <stappers at stappers.nl> wrote: > > > > Happy New Year! > > > > > > On Tue, Dec 30, 2014 at 05:29:29PM +0100, Geert Stappers wrote: > >> On Tue, Dec 30, 2014 at 09:34:57AM -0500, Michael Sumulong wrote: > >> > On Mon, Dec 29, 2014

Op 2013-12-11 om 02:09 schreef syslinux-bot for Matt Fleming: > Commit-ID: 5e59ac11d6d105591d6da742750ea2f804534d43 > Gitweb: http://www.syslinux.org/commit/5e59ac11d6d105591d6da742750ea2f804534d43 > Author: Matt Fleming <matt.fleming at intel.com> > AuthorDate: Wed, 11 Dec 2013 10:03:13 +0000 > Committer: Matt Fleming <matt.fleming at intel.com> >

Hi Thanks for confirmation about syslinux 6.02 requirements. I see small misunderstanding. A used word "Syslinux 6.02 BIOS" mean the respective syslinux binary files from "/bios" subdirectory for PC's with Legacy PXE or PC's with PXE where CSM mode is enabled. Some idea where is the issue? Do the syslinux 6.02 working well from PXE on multiple PC's in your place?

Another prerelease for the 5.00 (elflink) branch should be making its way to the mirrors now. The shortlog for -pre7 to -pre8 is listed below. Just like the 4.06 branch I was really hoping to drop a final release this week. Once 4.06 is out I'll merge that into 5.00. If you can, please test it out and let know any of any bugs you find. Because so much of the core infrastructure is rewritten

On Thu, Oct 31, 2013 at 6:32 PM, Marcin Celebucki <marcincelebucki at gmail.com> wrote: > Hi > > Thanks for confirmation about syslinux 6.02 requirements. > I see small misunderstanding. A used word "Syslinux 6.02 BIOS" mean the > respective syslinux binary files from "/bios" subdirectory for PC's with > Legacy PXE or PC's with PXE where CSM mode

On Tue, Dec 16, 2014 at 08:17:32PM +0100, Willem Bargeman wrote: > >> Hi, > >> > >> We have some problems while network booting thin clients. The type is T5540. > >> > >> At this moment we are using pxe linux 6.03. > >> > >> The systems are booting correctly with pxe linux version 6.03-pre14. > >> We have seen the same error

> On Saturday, January 17, 2015 9:34 AM, Gene Cumm <gene.cumm at yahoo.com> wrote: > > On Saturday, January 17, 2015 1:48 AM, Geert Stappers <stappers at stappers.nl> wrote: > > > > > > On Sun, Jan 04, 2015 at 07:37:44PM +0100, Geert Stappers wrote: > > > On Sun, Jan 04, 2015 at 12:14:51PM -0500, Gene Cumm wrote: > > <snip/>

Op 2014-06-12 om 06:43 schreef Geert Stappers: > Op 2014-06-10 om 22:55 schreef Geert Stappers: > > > > Hello, > > > > A `make efi32` yeilds me > > > > make[3]: *** No rule to make target `efi32/com32/lib/memcmp.o', needed by `syslinux.so'. Stop. > > make[3]: Leaving directory `efi32/efi' > > make[2]: *** [efi] Error 2 >

On Nov 30, 2013 7:33 PM, "Geert Stappers" <stappers at stappers.nl> wrote: > > Op 2013-11-30 om 13:12 schreef Gene Cumm: > <bigsnip/> > > > > Is there any chance you two could try my branch efi-fixes (commit > > d04b0edf) as I believe this solves the issues of the changing > > StationPort and routing difficulties of both a single subnet and

On Wed, Apr 27, 2016 at 12:43:37PM +0200, Geert Stappers via Syslinux wrote: > 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

On Wed, Oct 07, 2015 at 06:01:30PM +0200, Geert Stappers via Syslinux wrote: > On Wed, Oct 07, 2015 at 05:35:36PM +0200, Geert Stappers via Syslinux wrote: > > On Wed, Oct 07, 2015 at 08:55:53AM -0500, Clements, James wrote: > > > On Wed, Oct 07, 2015 Geert Stappers wrote > > > > 13:36:47.974245 IP 192.168.205.50.1939 > 192.168.205.1.tftp: 47 RRQ

On Sunday, January 4, 2015 12:53 PM, Geert Stappers <stappers at stappers.nl> wrote: > On Sun, Jan 04, 2015 at 03:14:51PM +0100, Geert Stappers wrote: > > > dmarc_moderation_action (privacy): Action to take when anyone posts > > > to the list from a domain with a DMARC Reject/Quarantine Policy. > > > > > > Wrap Message -- applies the

> On Saturday, January 17, 2015 1:48 AM, Geert Stappers <stappers at stappers.nl> wrote: > > > On Sun, Jan 04, 2015 at 07:37:44PM +0100, Geert Stappers wrote: > > On Sun, Jan 04, 2015 at 12:14:51PM -0500, Gene Cumm wrote: >?????????? <snip/> > > > As far as I can tell, GMail does process the SPF/DKIM/DMARC properties > > > but ignores

Op 2014-06-10 om 22:55 schreef Geert Stappers: > > Hello, > > A `make efi32` yeilds me > > make[3]: *** No rule to make target `efi32/com32/lib/memcmp.o', needed by `syslinux.so'. Stop. > make[3]: Leaving directory `efi32/efi' > make[2]: *** [efi] Error 2 It was encountered while doing `make`. The `make efi32` is just to faster reproduce the build

The setup I was using was in a chassis. Slot 8 of the chassis is the client machine. It goes through Switch 1 (a Brocade switch) to the top of rack (BNT). The mirror is in the chassis switch. Slot 3 of the same chassis is connected to the mirror port in Switch 1. client = 1/0/8 tcpdump = 1/0/3 to TOR = 1/0/43 1/0/8 mirrored both directions to 1/0/3 Unfortunately, I don't have access to the

On Tue, Oct 13, 2015 at 5:17 PM, Geert Stappers via Syslinux <syslinux at zytor.com> wrote: > On Sat, Oct 10, 2015 at 03:10:26PM +0300, Ady via Syslinux wrote: >> From: Geert Stappers <stappers at nero.gpm.stappers.nl> >> > >> > com32/mboot/map.c: removed trailing spaces >> > >> > They were introduced by the patch for ELF64 support. >>