similar to: SYSLINUX 2.07-pre5 OK?

Hi all, I have released SYSLINUX 3.35-pre5 to the Testing directory; this is a release candidate and I intend to release this as 3.35 early next week unless I hear of any showstopper bugs, so please, pretty please, try it out. http://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/ kernel.org has been overloaded lately, so it might take a while to show up. Changes in 3.35: *

Hi all, I have just pushed out SYSLINUX 3.55-pre5 and 3.60-pre7. I have decided to give them both release candidate status, with the intent of having a simultaneous 3.55 (bug fixes only) and 3.60 (new functionality) release. Please test them out and let me know how they do. -hpa

I have released SYSLINUX 3.08-pre5. Sparse files should now work correctly in extlinux. Symlink support still needs to be added, though. -hpa

Hi all, I have pushed out one more 4.03 prerelease; please help checking or testing it as I'm about to push a 4.03 out really soon. -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf.

I just encountered my only bug w/ the ISOLINUX+VESAMENU combination from 3.52-pre5. Updated a *working* CD project w/ the new ISOLINUX+VESAMENU combo just last week. Booting my preferred Linux distro (Slax-6) from my custom CDs work perfectly, however when I updated a CD project that includes BartPE/WinPE, BartPE fails to boot w/ 'CDBoot can not boot CD: error 4" msg. For the

Background: I recently wrote to Peter Anvin regarding IPAPPEND functionality, and he suggested I take the issue to this mailing list. I see it has been touched upon several times, after reviewing the archives. Let me see if I can add to it with a good level of detail: When using PXE to network boot a linux client, PXE must first acquire the client's IP address, by dhcp request, then, the

HPA, I believe I've found a possible bug with /menu. This against the unmodified -pre5 snapshot. SRC: http://www.survivaldisk.com/menutest.c COMPILED: http://www.survivaldisk.com/menutest.com It's easiest explained if you just compile the .c and experience it for yourself, anyways. If you have two submenus nested within each other and then call a third menu it will bring up the

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

I have just released SYSLINUX 2.09-pre4 with a few changes: a) SYSLINUX should now correctly handle mode changes from within a COMBOOT program. b) Tweaks to the menu system to avoid the "grey text on black" problem. c) A new color scheme for the menu system (Murali, check it out and see if you think it works for you.) ftp://ftp.kernel.org/pub/linux/utils/boot/syslinux/Testing/

SYSLINUX 3.11-pre5 is hereby a bug fix release candidate. If I don't receive any problem reports, I will release it as-is on Tuesday, August 30. http://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/ -hpa

Hello all, I just installed syslinux 2.10 on my usb-stick. It still boots then, but doesn't load initrd.gz (same config file..). Reverting back to syslinux 2.09 works fine, eg: initrd.gz is loaded. Something changed in initrd handling code? greetz, Jaap Crezee NB I am willing to share you more information or hints how to solve the problem. I am using kernel 2.6.7-bk20

The commit "linux.c32: move handling of mem= and vga= into the library function" also sets DEBUG to 1 in mboot.h. Is this intended? - Sebastian

hi: i try to make some images for pxelinux+memdisk. the version i try is 2.0.6 and 2.0.7pre5 for 2.88M floppy image, first i make a 1.44M boot floopy, then use "winimage" to load the disk and transfer it to 2.88M format, then save the image. it seems a easy way to make a 2.88M boot image. for harddisk image, i use vmware to build a virtual machine with 20M harddisk, make it boot

On 06/28/2013 04:07 PM, Gene Cumm wrote: > On Fri, Jun 28, 2013 at 12:53 PM, Gene Cumm <gene.cumm at gmail.com> wrote: >> On Fri, Jun 28, 2013 at 10:13 AM, Ady <ady-sf at hotmail.com> wrote: >> >>> But, in Syslinux 4.06, there is linux.c32, which is a sort of >>> introduction to Syslinux 5.xx (please allow me to be not strictly >>> accurate in

the following config-file triggers a couple of odd corner-cases in 3.08-pre5 ; SERIAL 0 19200 CONSOLE 0 APPEND console=ttyS0,19200n81 root=/dev/hda1 IMPLICIT 0 #DEFAULT sk1 #DEFAULT menu.c32 DEFAULT sk1 PROMPT 0 MENU TITLE Simple Boot Menu LABEL sk1 KERNEL vmlinuz-2.6.10-sk1 APPEND console=ttyS0,19200n81 root=/dev/nfs

This version contains a fix to mbr.asm, plus a version of Murali's menu system, but ported to gcc. Although gcc produces much bigger 16-bit code (since it's really 32-bit code with prefixes) I figured it would be much easier for people to deal with since it requires the configuration to be compiled in. That being said, it's a *very* powerful menu system, partially *because*

Goodness, how many prereleases has there been in the last week... have lost count... Anyway, I have implemented the already-promised chainbooting API, and have included a sample program to chainboot floppies (it works for harddisks too, but only for the MBR.) As a bonus, in the process I actually discovered that booting .bs/.bss images under SYSLINUX was actually broken... that has been

Hi! as i know that you like test reports, here are some... Testing environment: CompactFlash card, connected with an USB adapter to a Compaq Evo D310 frontal USB port. This machine boots via USB quite well with syslinux. 3.09 boots ok, no problem 3.10-pre2 does not boot 3.10-pre3 does not boot 3.10-pre4 does not boot 3.10-pre5 locks up pc 3.10-pre6 locks up pc 3.10-pre7 writes

I apologize for the long delay in testing this. I can only reproduce the problem on fancy new laptops, and those do not stay in my hands for very long. As you may recall, certain floppyless laptops have a BIOS bug which prevented them from working with MEMDISK. Around a month ago, Robert Wruck contributed workaround patches, and hpa included a modified version of them in 2.07-pre1. He asked

On Oct 17, 2014, at 1:30 PM, "H. Peter Anvin" <hpa at zytor.com> wrote: > >> On 10/17/2014 12:19 AM, Ferenc Wagner wrote: >> "H. Peter Anvin" <hpa at zytor.com> writes: >> >>> I would like to do a short cycle for 6.04, because 64-bit support for >>> ext4 has come up as a very high priority. Therefore I do not want to