similar to: SYSLINUX 3.11-pre11 -- release candidate

Im trying to use newer simple-menu features, and have found that the following config-file (closely based on wiki pxelinux example) - fails for 3.62-pre11, - works for 3.62-pre10 where 'working' is successive reloads such that re-edits of file are seen on next reload and broken is issuing this error: Initial menu has no LABEL entries! boot: #>

Hi all, I have decided to declare 2.12-pre11 a release candidate. I'd appreciate any and all testing anyone can do on this version. Hopefully the "2.20" rewrite of the FAT-based SYSLINUX will come not too long thereafter. ftp://ftp.kernel.org/pub/linux/utils/boot/syslinux/Testing/ -hpa

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

Peter, Paulo reported some problems with his config files under ISOLINUX and PXELINUX - basically TIMEOUT and TOTALTIMEOUT were broken. The patches I've pushed to the elflink branch fix this and also fix parsing of the ALLOWOPTIONS config directive. The following changes since commit d5e02fb16a11bfdbce1e90a39e6cb5f2ad925389: get_key: Valid key values are positive (2012-04-17 11:25:53

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

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 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

I just started to play with syslinux 3.11 and have some problems with the configuration. I want to implement following: wait 5 seconds till the users chooses the right label. if nothing is done for 5 seconds it should boot from next boot device specified by the BIOS. I configured syslinux like that: default menu.c32 prompt 0 timeout 50 ONTIMEOUT localboot totaltimeout 200 display boot.msg MENU

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

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

Follow up, While awaiting my initial message to clear the moderator, as my company's Exchange server tacked on some bogus header, I downloaded version 3.08-pre11 (vs the 3.07 I was using). This newer version seems to work correctly. - Rick

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

Changes in 3.11: * MEMDISK: Fix bug by which accessing the real floppy disk as B: in MS-DOS was broken. * Simple menu system: allow tweaking of the screen layout. * Simple menu system: better command-line editing, correctly handle command lines above 256 characters. * PXELINUX: revert memory allocation change that caused problems

Jim, I think the main point of Tomas' post was to alert R users to the fact that there are very serious issues that you have to understand when interfacing R from C++. Using C++ code from R is fine, in many cases you only want to access R data, use some library or compute in C++ and return results. Such use-cases are completely fine in C++ as they don't need to trigger the issues

Kevin, > On Mar 29, 2019, at 17:01, Kevin Ushey <kevinushey at gmail.com> wrote: > > I think it's also worth saying that some of these issues affect C code > as well; e.g. this is not safe: > > FILE* f = fopen(...); > Rf_eval(...); > fclose(f); > I fully agree, but developers using C are well aware of the necessity of handling lifespan of objects

I am having difficulty trying to figure out how to get a computer to boot from it's local disk automatically after the pxe menu times out. I installed syslinux-3.11-4 with yum onto CentOS 5.5 It boots to the local disk if I select Local from the menu and press enter but it never times out and boots localy. The AUTOBOOT message doesn't appear either. Which instructions in the PXELINUX

First, thank you to Tomas for writing his recent post[0] on the R developer blog. It raised important issues in interfacing R's C API and C++ code. However I do _not_ think the conclusion reached in the post is helpful > don?t use C++ to interface with R There are now more than 1,600 packages on CRAN using C++, the time is long past when that type of warning is going to be useful to the

I think it's also worth saying that some of these issues affect C code as well; e.g. this is not safe: FILE* f = fopen(...); Rf_eval(...); fclose(f); whereas the C++ equivalent would likely handle closing of the file in the destructor. In other words, I think many users just may not be cognizant of the fact that most R APIs can longjmp, and what that implies for cleanup of

On May 13, 2014 4:04 PM, "Ady" <ady-sf at hotmail.com> wrote: > > 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. > > I don't believe it can be used as is: > > bash# file syslinux > > syslinux: ELF 32-bit LSB executable, Intel 80386, version

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