similar to: Syslinux-6.00-pre2

I know everyone is itching to test out another prerelease, and there's been quite a lot of activity since the last one. The shortlog is appended below. The feedback from testing the previous prereleases has been really constructive, so thanks to everyone for that. That feedback has been addressed in some of the commits listed below, but it's not all bug fixes, we've also got some new

Finally, the Syslinux 6.00 release is out. This release includes support for booting from EFI, both from disk-based media and over the network via PXE. Thanks to everyone who has been testing this out. There are some EFI bugs that I'm aware of, * booting Linux kernels without CONFIG_RELOCATABLE doesn't work * 64-bit syslinux.efi cannot boot 32-bit kernels and vice versa *

Attached are 4 patches against Syslinux 4.06 providing two new options for the linux.c32 ComBoot32 module. If we are shifting gears towards 4.10 or 5 any time soon, feel free to let me know and I'll attempt to apply the patches to those and to deal with any conflicts. You can merge these commits onto your 4.06 from my 'multi_initrd' branch at:

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,

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:

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

On Sun, 23 Jun, at 11:21:45PM, Gene Cumm wrote: > Correction: simple menu always does decimal (as should be expected). > > >> com32/elflink/ldlinux/readconfig.c: > >> } else if ((ep = looking_at(p, "ipappend")) || > >> (ep = looking_at(p, "sysappend"))) { > >> uint32_t s = strtoul(skipspace(ep),

From: Matt Fleming <matt.fleming at intel.com> Here are the patches that I've got queued up based on the very helpful feedback I received from people testing Syslinux 5.00-pre9. Unless anyone has any concerns these will make it into Syslinux 5.00-pre10. Matt Fleming (9): pxe: Don't call open_config() from the pxe core ldlinux: Print a warning if no config file is found

On Fri, Jun 10, 2016 at 2:06 AM, Adam Goldman via Syslinux <syslinux at zytor.com> wrote: > PXELINUX has stopped recognizing the keeppxe option on the kernel > command line. Here is a patch to make it work again. > > With COM32, it is no longer possible to use preprocessor directives to > determine the SYSLINUX variant. The code inside the #if will never be > compiled. So,

I've just pushed out a 6.00-pre1 release. This release includes support for booting EFI machines. The code is currently in the alpha stage. Having said that, you should expect most things to work correctly, including things like the graphical menu. Please help test if you can, and if you find any bugs, please report them. To facilitate building different versions of syslinux.efi (32-bit and

I've been working with Matt Burgess here on this problem, and have found the following: syslinux 3.08-pre10 ? broken >>> config.inc:max_cmd_len=255 syslinux 3.08-pre11 ? works >>> config.inc:max_cmd_len=1023 syslinux 3.08 ? works >>> config.inc:max_cmd_len=1023 syslinux 3.09-pre1 ? works >>> config.inc:max_cmd_len=1023 syslinux 3.09-pre2 ? broken

Hi folks My ultimate goal is to be able to add an initramfs to the end my syslinux.cfg resulting in an additional initramfs being loaded when the system boots. So I need to work out how to get initrd+= to work. I?ve been trying for days now everything I possibly can to get initrd+= to work but nothing I do works. I've also been trying to get initrdfile= to work but no success with that

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

On Tue, Mar 11, 2014 at 11:08 AM, Eric PEYREMORTE <eric.peyremorte at iut-valence.fr> wrote: > Le 11/03/2014 15:27, Ady a ?crit : > >>> Le 11/03/2014 10:32, Eric PEYREMORTE a ?crit : >>> Some news here. I didn't test with 5.01 yet (didn't see that one sorry). >>> With 5.01 i don't have any problem. Problems begin with 5.10. >>> --

PXELINUX has stopped recognizing the keeppxe option on the kernel command line. Here is a patch to make it work again. With COM32, it is no longer possible to use preprocessor directives to determine the SYSLINUX variant. The code inside the #if will never be compiled. So, I changed it to use syslinux_filesystem() to determine the variant. Also, I moved the relevant code from

> >> Hello Ady, > >> > >> To sum up : > >> > >> > >> _ 4.0x works; > >> _ 4.10-pre22 (lwip branch) works; > >> _ 5.01 (elflink branch) works; > >> _ 5.10 and beyond (lwip merge into elflink) fails; --> pxelinux.0 very slow, > >> lpxelinux.0 freezes (i don't get the menu) > >> > >> I

Le 11/03/2014 17:54, Gene Cumm a ?crit : > On Tue, Mar 11, 2014 at 11:08 AM, Eric PEYREMORTE > <eric.peyremorte at iut-valence.fr> wrote: >> Le 11/03/2014 15:27, Ady a ?crit : >> >>>> Le 11/03/2014 10:32, Eric PEYREMORTE a ?crit : >>>> Some news here. I didn't test with 5.01 yet (didn't see that one sorry). >>>> With 5.01 i

Hi Peter, The main part of this pull request includes commits that try to replace as many __intcall() invocations as possible. Some remain, but not many (and eventually they'll be gone too). There's also a patch to make better use of ld's --as-needed option and various other bug fixes/cleanups. The following changes since commit ff7334a2ce536b7f4b1f6d6f93ff4e285a3bd45a: Only

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

> Le 11/03/2014 10:32, Eric PEYREMORTE a ?crit : > Some news here. I didn't test with 5.01 yet (didn't see that one sorry). > With 5.01 i don't have any problem. Problems begin with 5.10. > -- > Eric PEYREMORTE Hello Eric: To sum up your report: _ 4.0x works; _ 4.10-pre22 (lwip branch) works; _ 5.01 (elflink branch) works; _ 5.10 (lwip merge into elflink) fails; I