similar to: 2.12-pre11 is release candidate

I ended up implementing the "totaltimeout" command per discussion on the SYSLINUX mailing list, and adjusted the timeout of the menu system accordingly. The necessary restructuring really wasn't too painful with judicious use of longjmp() and subroutines -- basically poor man's exception handling. Thus, I have released 3.11-pre11; barring no objections or problems I will

Tried both normal and debug images with Roxio 6 and Nero 6.6. Everything worked fine. Also tried cdrwin and ran into an interesting issue with it regarding it's support of image files >8k -- reported it to them. FYI, tried booting on 2 Intel and 2 Asus planars all reported no info returned in the spec packet. David >Okay, after a bit more research I ended up implementing this

> On Tue, May 13, 2014 at 7:51 PM, Ady <ady-sf at hotmail.com> wrote: > > > > I wonder why the already built-in binaries are not enough / adequate. > > Or, in other words, I am curious about why do you need to build your > > own binary files, instead of using the files that are already there > > in the official archives in kernel.org. > > I don't

Hello everyone, I have pushed out SYSLINUX 3.08. It's identical in all but version number to 3.08-pre11. Sorry for everything that probably should have been done that didn't make it, but I simply haven't had time :( :( :( However, given several bugs fixed in 3.08, this seemed important... Changes in 3.08: * SYSLINUX: Fix performance regression (-s mode always

I have released SYSLINUX 2.08-pre11. It is the same as 2.08-pre10 except I have added logical partition support to the chainbooting module (still no partition hiding or anything like that.) Unfortunately I have no way to test this at the moment, so I thought I'd release a -pre11 and see if someone was willing to take it for a spin.

On Tue, May 13, 2014 at 11:52 PM, Gene Cumm <gene.cumm at gmail.com> wrote: > make bios clean > make bios installer > > This should satisfy your goal. bash$ git clone git://git.zytor.com/syslinux/syslinux.git syslinux-6.03-pre11 bash$ cd syslinux-6.03-pre11 bash$ make bios clean ... bash$ make bios installer make -r -C /sources/syslinux-6.03-pre11 -f

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

Hey folks, I was trying the complex menu from the lastest pxelinux 3.20-pre11. It did install a password file in the /isolinux/ of my tftpserver. Then I try to authentificate myself as user3 with as password I've been tranforming using sha1pass. When I select login, the screen blink and doesn't ask me anything. I reslect login, it ask me for a username. I give user3 and then my

Hi all, I have released SYSLINUX 2.09-pre11; the only difference is Murali's latest patches for the menu system, mostly to add the ability to add separators to the menus. ftp://ftp.kernel.org/pub/linux/utils/boot/syslinux/Testing/ Please test it out. Some time over the weekend I'm going to do a sweep for bug fixes I've forgotten and otherwise I'd like to release 2.09 next

This test release includes the Multiboot support from Tim Deegan, and increases the command line limit to 1023 characters. This is a 3.08 release candidate, so if you have a chance, please test it out. ftp://ftp.kernel.org/pub/linux/utils/boot/syslinux/Testing/ -hpa

I have just pushed out SYSLINUX 3.10-pre11. This version hopefully should fix Curtis' bug (display file garbage) as well as the NOESCAPE problem. Curtis, Alex and Paul, could you try this version out, please? -hpa

Hey, I just wanted to mention that the same problem still exists for me in version 3.09, altough the changelog mentions: Reduce the command line to 511 characters; 1023 caused memory overflows. Was this meant to be a solution for this problem, or does this entry of the changelog apply to another bug? thx, marco >Yesterday Curtis Doty said: > > > >>I've begun

Let's try to get this thing released. Dag: will you do your RPM buildathon on this drop? Changes in 3.74: * New UI directive, which allows a more natural way to specify a menu system (or not.) With the UI directive specifying the menu system, the DEFAULT directive can be used to select the default entry inside the menus. * kbdmap.c32: new module

On May 13, 2014 6:02 PM, "H. Peter Anvin" <hpa at zytor.com> wrote: > > On 05/13/2014 02:52 PM, Gene Cumm wrote: > > > > Alexey: > > > > make bios clean > > make bios installer > > > > This should satisfy your goal. > > > > I don't *think* you want the bit "bios" in there... > > -hpa That

On May 13, 2014 6:14 PM, "H. Peter Anvin" <hpa at zytor.com> wrote: > > On 05/13/2014 03:07 PM, Gene Cumm wrote: > > > > That should make "make" ignore efi32 and efi64. > > > > Normally when you specify two things on the "make" command line it tries > to build both, i.e.: > > make bios clean > > ... is

On Tue, 13 May, at 06:43:11PM, Gene Cumm wrote: > On May 13, 2014 6:14 PM, "H. Peter Anvin" <hpa at zytor.com> wrote: > > > > On 05/13/2014 03:07 PM, Gene Cumm wrote: > > > > > > That should make "make" ignore efi32 and efi64. > > > > > > > Normally when you specify two things on the "make" command line it

On 05/13/2014 03:07 PM, Gene Cumm wrote: > > That should make "make" ignore efi32 and efi64. > Normally when you specify two things on the "make" command line it tries to build both, i.e.: make bios clean ... is (almost) the same thing as ... make bios make clean -hpa

With some help from Nathan Laredo, I cribbed my way though porting the Win32 installer on my own accord. Thus, I believe we now have something which can be called a release candidate. Given how much stuff managed to make it in, after all, I'm seriously considering calling it 3.00, but for now it's 2.20-pre13. So, everyone that can, please test it out. In particular, I have not yet

On Tue, May 13, 2014 at 7:51 PM, Ady <ady-sf at hotmail.com> wrote: > > I wonder why the already built-in binaries are not enough / adequate. > Or, in other words, I am curious about why do you need to build your > own binary files, instead of using the files that are already there > in the official archives in kernel.org. I don't believe it can be used as is: bash# file

Hi all, I have received a fair number of bug reports over the last few weeks -- even days -- and I am therefore declaring 3.53-pre5 a release candidate for a 3.53 bug fix release. This 3.53 will not contain either of the two major features under development -- client side state (including boot-once) and gPXE integration -- since I want to avoid destabilizing the code base beyond the bug