similar to: Apologies for being absent...

Thanks to debugging information from Thomas Mieslinger, I have root-caused the failure of chain.c32 in Syslinux 3.85. I have put out Syslinux 3.86-pre1 and Syslinux 4.00-pre33 which fix the problem. I expect to release a Syslinux 3.86 relatively shortly (ideally in the next two weeks), with bug fixes only. I would like to figure out if there are other bug fixes we can get in in reasonable time,

On 10/13/2010 08:36 AM, syslinux-bot for Michal Soltys wrote: > Commit-ID: 9c8db7560e2dc83d1191bb2f90b4d4d0ae3d37d6 > Gitweb: http://syslinux.zytor.com/commit/9c8db7560e2dc83d1191bb2f90b4d4d0ae3d37d6 > Author: Michal Soltys <soltys at ziu.info> > AuthorDate: Wed, 13 Oct 2010 10:57:36 +0200 > Committer: Michal Soltys <soltys at ziu.info> > CommitDate: Wed, 13

Hi everyone, I have pushed out Syslinux 3.81 to the usual places. Again, special thanks to my employer, Intel, for letting me spend time working on this stuff ;) -hpa Syslinux 3.81 is primarily a bug fix release. The main new features are halt-on-idle support and some features to isohybrid, including the ability to boot from an image written to a partition. Changes in 3.81: *

So far, the consensus seem to be: - Devel list is not desirable at this time. I will continue to post major announcements to syslinux-announce, of course. - The 4-space coding standard seems to get most favor. I would like to run reformatting jobs immediately after the 3.81 release; the expectation is that other people will run the same reformatting on any code merged after that point

On 03/08/16 08:58, Shao Miller via Syslinux wrote: > While building on AMD64 CentOS 6, I noticed that glibc-devel.i686 was > needed for some (U)EFI stuff, but isn't in the README. I'm not sure if > other Linux flavours will have counterpart needs. - Shao Hmmm... that makes me somewhat nervous. I'm wondering if we're pulling in stuff we should not. -hpa

Two additions to MEMDISK to support OS drivers. The "safe hook" structure ("Safe Master Boot Record INT 13h Hook Routines") is a means for an OS driver to follow a chain of INT 13h hooks, examining the hooks'' vendors and assuming responsibility for hook functionality along the way. For MEMDISK, we guarantee an additional field which holds the physical address for the

Hi all, I would like to release Syslinux 4.02 TODAY. If there is anything I'm missing, or which is wrong in Syslinux 4.02-pre3, please scream loudly NOW... -hpa

Just a slight poke regarding the MEMDISK and MDISKCHK.COM possibilities available here[1]. Review by non-hpas is welcome, too. Thanks! - Shao [1] http://git.zytor.com/?p=users/sha0/syslinux.git;a=shortlog;h=refs/heads/ mdiskchk_enh2

Given the number of people that are starting to be involved in Syslinux development, I wanted to start a discussion about a common coding style, for C code in particular. Currently, a lot of the code in Syslinux is written in different styles, partly because my own style has changed over the years. There are pretty much two alternatives that I think are realistic: a) Linux kernel coding style:

Hi Folks, I'm interested in "headless" installation. If I use GRUB, then I provide arguments to the kernel of things like "headless vnc vncpassword=whoopie ip=dhcp" GRUB passes this on to ISOLinux, which manages the CD and subsequently the installation. Shouldn't I be able to do exactly the same thing with EXTLinux? I ask, because, as you might suspect, I

Hello, (1) You are requested to provide the link to download a file that contains "Isolinux.cfg/Syslinux.cfg" with necessary "colour scheme". (2) If accepted, requested to provide such a file in Syslinux-3.87 on wards Prof S W Damle

I'm preparing a few simple patches that will cleanup few things regarding new chain - in particular the ones I mentioned in Januray during discussion with Shao (tone down overkill abstractions, etc.). One question on a formal side though - which license is preferred at the top of the source files ? Currently there're two present - either something bsd-ish (on parts derived from

Improving chain.c32 help message Impact: Error message is more detailed In case of syntax error, the message is far more detailed and provides the same content as the documentation integrated in the source code. You can get this patch from Erwan's git repo: http://git.zytor.com/?p=users/erwan/hdt.git;a=commit;h=3fc3126d0c7df5701680e043c34f200166f24564 Add 'isolinux=' option to

Good day to all, Gert Hulselmans requested a feature for MDISKCHK.COM that would function roughly like GETARGS.COM[1] by Murali Krishnan Ganapathy: DOS SET command output for MEMDISK kernel arguments passed by previous boot-loaders. He also needed to support the case for MEMDISK-in-a-MEMDISK type situations, where all MEMDISK kernel arguments could be gathered together and output as a list

For the boot floppy at http://superkeen.com/peacecorpsfiles/FUZOMA14.IMG using memdisk from syslinux version 3.72 boots correctly, but for memdisk versions newer than 3.72 (I tested 3.73, 3.75, 3.85, and 3.86) all hang at boot with the following message: Loading boot sector... booting FreeDOS kernel - SVN (build 2039 OEM:0xfd [compiled Oct 2 2009]) Kernel compatibility 6.22 - BORLANDC ... XMGR,

Randy McAnally wrote: > > Thank you so much, this is the kind of news I needed! > > ---------- Original Message ----------- > From: "Arends, R.R." <r.r.arends at hro.nl> > To: "Randy McAnally" <rsm at fast-serv.com> > Cc: <gpxe at etherboot.org> > Sent: Wed, 03 Mar 2010 10:10:56 +0100 > Subject: Re: [gPXE] localboot 0 hang on some

Hello everyone, I recently made a 64-bit build of R-2.2.1 under Solaris 9 using gcc v.3.4.2. The server has 12GB memory, 6 Sparc CPUs and plenty of swap space. I was the only user at the time of the following experiment. I wanted to benchmark R's capability to read large data files and used a data set consisting of 2MM records with 65 variables in each row. All but 2 of the variables are of

For anyone wanting to boot an .ISO with MEMDISK: http://git.etherboot.org/?p=people/andytim/syslinux.git;a=shortlog;h=ref s/heads/memdisk-iso NOTE: Your protected-mode OS (Windows, Linux, *BSD) booted from such a MEMDISK will not magically find the MEMDISK image in RAM and use it as a CD without a MEMDISK driver. There are currently 0 MEMDISK drivers in the field, but that might change someday.

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:

On 03/08/16 09:41, Shao Miller wrote: > On 3/8/2016 12:31, H. Peter Anvin wrote: >> On 03/08/16 08:58, Shao Miller via Syslinux wrote: >>> While building on AMD64 CentOS 6, I noticed that glibc-devel.i686 was >>> needed for some (U)EFI stuff, but isn't in the README. I'm not sure if >>> other Linux flavours will have counterpart needs. - Shao >>