similar to: Fwd: ext3 for pre7 ?

Gene, Where did you find the precompiled binaries for syslinux 6.03-pre7? Actually, I'm interested in the pre-compiled binaries for syslinux 6.03-pre6. I went out to kernel.org, but the latest they have is 6.02. Which appears to have an endian problem in its TFTP client code (when syslinux.efi tries to connect to the TFTP server, attempts to connect to UDP port 17664 instead of 69).

-------------------------------------------- On Thu, 7/4/13, Matt Fleming <matt at console-pimps.org> wrote: Subject: Re: [syslinux] Syslinux 5.11-pre7 not working To: "Shantanu Gadgil" <shantanugadgil at yahoo.com> Cc: syslinux at zytor.com Date: Thursday, July 4, 2013, 4:51 PM On Wed, 03 Jul, at 11:22:27PM, Shantanu Gadgil wrote: > Hi, > > I am a happy

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

Hi all, I have merged Tim's patches to the mboot loader, and have pushed it out as 3.20-pre7. I guess I'm going to actually have to make a 3.20 here soon... -hpa

I just uploaded SYSLINUX 3.72-pre7. I'm hoping this will be the final 3.72 prerelease. Please test it and holler if something is (still) broken. -hpa

Hi, I am a happy user of version 4.06 and have been hoping to upgrade the 5.x series (for the HTTP bits). I have the following problems with the 5.11-pre7 build: 1. TFTP load is horribly slow ... even when the two REAL machines are connected to the same switch. For a typical RHEL installation, the vmlinuz loads ... the initrd.img loads very very slowly and just times out (I waited over 10 mins)

I'm going to promote SYSLINUX 3.32-pre7 to release candidate unless someone objects, with the intent of releasing 3.32 immediately after Christmas. Please let me know if there are problems that should make me *not* do so, even if you have previously reported them. -hpa

I have just pushed out Syslinux 3.80-pre7. I am slightly concerned about putting this into the release tree at this point: I was working with some of the shuffler code, and found that the memory map handling was actually severely buggy on some of my test cases. Resolving that problem took rewriting most of syslinux_add_memmap(). However, against better judgement :) I decided to check in the

I''ve just uploaded 0.9.11-pre7. save/restore should be working for 32 bits on both SMP and UP, and maybe for 64 bits although it''s not tested. If someone could test migration it would be much appreciated. The installer seems to not install the drivers under 64 bit environment... but they can then be installed manually. Not sure why at this point.

I''ve just uploaded 0.9.11-pre7. save/restore should be working for 32 bits on both SMP and UP, and maybe for 64 bits although it''s not tested. If someone could test migration it would be much appreciated. The installer seems to not install the drivers under 64 bit environment... but they can then be installed manually. Not sure why at this point.

Hi all, and particularly Andrew and Stephen, I recently "upgraded' one of my NFS fileservers from (patched)2.4.18 to 2.4.23-pre7 (in order to resolve a HIMEM related memory pressure problem). Unfortunately I have experienced what appears to be a deadlock. The one I will describe was experienced while running 2.4.23-pre7, though I had a very similar problem in 2.4.22 (but

On Thu, Jul 4, 2013 at 10:44 AM, Shantanu Gadgil <shantanugadgil at yahoo.com> wrote: > On Thu, 7/4/13, Matt Fleming <matt at console-pimps.org> wrote: > > Subject: Re: [syslinux] Syslinux 5.11-pre7 not working > To: "Shantanu Gadgil" <shantanugadgil at yahoo.com> > Cc: syslinux at zytor.com > Date: Thursday, July 4, 2013, 4:51 PM > > On

Still interested in pre-compiled binaries for 6.03-pre6. But my comment about 6.02 TFTP brokenness may speak more to my lack of understanding of the TFTP protocol than to any pxelinux 6.02 code problems. It seems that when TFTP sends an OACK back to syslinux.efi, it sends it from another port than 69. So, it seems to be opening a data connection back to the TFTP client off an ephemeral port.

Hi all... First of all, I'm new to this list. Thanks in advance for the help I surely will get here ;) I have installed a CentOS 5.2 64 bit on a computer, and I can't get it to boot. The box is a custom built computer, with this components: - ASUS P5N64 WS Pro motherboard (nForce 790i Ultra SLI) More details here:

Hi all, I've decided to move SYSLINUX 3.30-pre7 to release candidate status (the difference from 3.30-pre6 is pretty much that 3.30-pre7 contains a very simple compiled-in graphical background if the user doesn't specify MENU BACKGROUND.) Please test it out and let me know. Thanks, -hpa

I have just released SYSLINUX 1.75-pre7. Barring any showstopper bugs, this WILL be the final 1.75, so please test if out, and if you find problems speak now or forever hold your pizza. After 1.75 is out I'm going to be spending most of my time on the new 2.00 release. http://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/ -hpa

> > Alright... I have released SYSLINUX 1.76-pre1 and 2.00-pre7 with this > > workaround included; please test and I'll promote 1.76-pre1 to 1.76 if > > it works. > > I can test only in couple of days... I.e. on Toshiba... it does. a.

Hi all, I have released SYSLINUX 2.08-pre7. This version rate-limits the ARP polling in PXELINUX; it turns out that it was giving people using automatic control via serial console a real headache since it caused PXELINUX to drop characters. As usual, I'd really appreciate any and all testing. ftp://ftp.kernel.org/pub/linux/utils/boot/syslinux/Testing/ -hpa

Ok folks... SYSLINUX 2.08-pre7 is hereby declared a release candidate. Please test it out; if it works for people I'll promote it to 2.08. -hpa

Hi all, Being able to switch between config files has been a long-requested feature. Well, in syslinux-3.40-pre7 I think it's finally implemented in a way which can be classified as "working". If you have a need for this feature I would like your opinions, including whether or not the implementation as it stands fits your liking. -hpa