similar to: I heard the patch window was open? Two small patches

I've been trying to get syslinux.efi working in my environment again... Found what look like a bunch of little bugs that are very frustrating... First, the documentation on the Wiki says that as of 5.11, the list separator is space, not colon. But I can find no evidence that 5.11 was ever officially released or that a commit to git was made to make this change. 6.00 and following still use

Phil, I gave a presentation last month on how to set up a DHCP + TFTP server. Using syslinux 6.03-pre* to support both Legacy and EFI PXE boot. Here's the link to the presentation. My slides are there. http://2014.texaslinuxfest.org/content/creating-legacy-efi-pxe-server-using-pxelinux The presentation models a small lab-sized env. I start simple; supporting legacy PXE boot only. Then

I am trying to use rsync (3.0.6) to keep two directories as exact duplicates. I would normally run: rsync -av -S --delete /path/to/src/ /path/to/dst/ to do this. Unfortunately, the directories have become rather large (2TB, a million files) and so the tree walk has become a prohibitively time consuming part of the operation. However, I have a way to generate a list of file changes

>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

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

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

Sounds like we should change the "and cx" mask to 5 so that if either EHDD support or LBA is announced by the bios, the correct EHDD path will be taken. Phil P. -- Philip Pokorny, RHCE Chief Technology Officer PENGUIN COMPUTING, Inc www.penguincomputing.com Changing the world through technical innovation

Hello, I see lots of current activity trying to get EFI PXE working both with new and "old" kernels (RHEL 6.5) and lots of failures. I've got several real pieces of hardware (AMD APU, Intel E5-2600, etc.) with a variety of BIOS and NIC that have EFI PXE stacks to test with. But I find zero documentation that's up to date on the wiki of how to configure a DHCP server to send

Hello, I'm looking for and offering help. I know this has been an on-going problem and I thought I had seen a fix go by, but I'm compiling from the latest github.com/geneC/syslinux and syslinux.cz repositories and I've got a system which doesn't work. It does DHCP and gets a filename "efi/syslinux.efi" and downloads that correctly. It then executes it which clears the

> > Date: Mon, 8 Aug 2016 15:05:17 +1000 > From: Michael Davies <nemykal at nrv-linux.io> > To: syslinux at zytor.com > Subject: [syslinux] Syslinux Aarch64 porting > Message-ID: <05476825-bf5e-9898-4aaa-3eaa927bbd0c at nrv-linux.io> > Content-Type: text/plain; charset=utf-8; format=flowed > > Hi, > > Is there any information available on porting

> Attached is a patch for the latest tftp-hpa. > This patch add support for named pipes. > > Named pipes are 0 byte files which can be read by a PXE boot process. > They provide the necessary informations for the boot process and are > deleted afterwards. > This PXE boot is a single event and won't interact until another named > pipe is created for the client.

This document: http://www.iana.org/assignments/dhcpv6-parameters/dhcpv6-parameters.xml Has the same (plus expanded) list of cpu arch values for parameter 0x93. This list matches RFC 4578 except for values 7 and 9 which are EFI ByteCode and x86-64. Turns out RFC 4578 is wrong https://www.rfc-editor.org/errata_search.php?rfc=4578 And 00:07 *is* the correct value for 64-bit x86 clients and the

I asked before about config_cwd and after some more digging, it looks like it could be removed... Specifically, the documentation http://www.syslinux.org/wiki/index.php?title=Config#CONFIG says: ---------- * CONFIG config_file [new_WD] Load a new configuration file. The new configuration file is read, the Working Directory is optionally changed (if specified via an optional second parameter),

Hello, The description of SYSAPPEND for the DMI information states that the spaces are replaced by underscores, but this replacement does not occur in 6.03. There's small bug present in triplicata in com32/elflink/ldlinux/readconfig.c:copy_sysappend_string(), com32/menu/readconfig.c:copy_sysappend_string(), and core/sysappend.c:copy_and_mangle() prevent proper replacement of spaces by

To remind you once again. ISOLINUX >= 6.00 built with GCC >= 5.0.0 causes a broken boot. This relates specifically to the use of the vesamenu.c32, menu.c32 works without problemos. This "code" is already in 6.03, therefore this is not a fix for it! Revert "SYSAPPEND: Fix space stripping" This reverts commit 3106dcd http://repo.or.cz/w/syslinux.git/commit/3106dcd Fixes

Hi! I have just tried to build menu.c32 but it fails. 3.20pre3 works fine though. Here is what happens: bash-3.1$ make gcc -m32 -mregparm=3 -DREGPARM=3 -W -Wall -march=i386 -Os -fomit-frame-pointer -I../libutil/include -I../include -D__COM32__ -c -o menu.o menu.c menu.c: In function `run_menu': menu.c:549: warning: variable `done' might be clobbered by `longjmp' or `vfork'

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-03:06.openssl Security Advisory The FreeBSD Project Topic: OpenSSL timing-based SSL/TLS attack Category: crypto Module: openssl Announced:

On Wed, 12 Jun, at 11:17:44AM, Gerardo Exequiel Pozzi wrote: > Cool thanks!. Now looks better, but still not work. > > For some reason, "ldlinux.c32" is apparently sent but "Failed to load" > by PXELINUX and few seconds later, dnsmasq shows an error message > "failed sending": Argh! The patch was broken. I missed the new core/path.c file. My bad.

On 03.07.2015 12:28, Gene Cumm wrote: > On Fri, Jul 3, 2015 at 12:50 AM, poma via Syslinux <syslinux at zytor.com> wrote: > >> - "unsigned char c;" does not solve the problem >> >> - "c >= 0 && c <= ' '" solves the problem for the current git > > Could you try the following patch? Feel free to only apply the change

com32/modules/readconfig.c: This is a side effect of is_kernel_type() overwrite the current pointer in a loop context. Hence subsequent options aren't parsed ever. This is particularily visible, if you use timeout option, which wont work in the latest 3.40-pre7. Patch: --- com32/modules/readconfig.c /opensource/syslinux-3.40-pre7/com32/modules/readconfig.c#2 +++ com32/modules/readconfig.c