similar to: SYSLINUX 3.50-pre14 pushed out; adds INCLUDE support

If there is anything that you think should have been in Syslinux 4.04 which isn't there please holler now. -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf.

I have addressed all the issues that I know about (including, hopefully, the isohybrid version dependence...). I would like to release this this week so please let me know as soon as possible if this version is "go". -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf.

This version fixes the "PXELINUX reboots immediately on error" problem. This actually turned out to be due to a NASM bug; I have changed the code slightly to avoid the problem. Please, people, test this out so I can release a final... ftp://ftp.kernel.org/pub/linux/utils/boot/syslinux/Testing/ -hpa

Hi all, I have finally gotten SYSLINUX 3.50 what it feels like feature-complete for release, or something pretty close to it. As a consequence, I am declaring 3.50-pre16 a release candidate. Here is what's news since 3.36: Changes in 3.50: * New keywords allow the type of file to be specified in the configuration file. * It is now supported to load a different

Well, SYSLINUX 3.50 has been in development since September of last year (it was originally a branch off 3.31), and the diff against 3.36 is almost 15,000 lines. I doubt it's going to be bug free, but prereleases can only get you so far with respect to testing. Thus, it's time to push the button and getting this thing out into the world. I hereby announce SYSLINUX 3.50. Special thanks

I just tried to build syslinux-3.71-pre14-5-gfa6a60e and got the following: make[1]: Leaving directory `/syslinux/syslinux-3.71-pre14-5-gfa6a60e/dos' make[1]: find-mingw.sh: Command not found make[1]: Entering directory `/syslinux/syslinux-3.71-pre14-5-gfa6a60e/win32' gcc -Wp,-MT,syslinux.o,-MMD,.syslinux.o.d -W -Wall -Wno-sign-compare -Os -fomit-frame-pointer -D_FILE_OFFSET_BITS=64 -I.

So it turns out that -pre13 was quite buggy after all. Once I started running the list of tests that I described in my email, a bunch of those bugs came to heed. Now I think I've fixed them, and so have released -pre14. I have also formally decided to call the final release 3.00 when it's ready. Between code base rewrite + EXTLINUX + libcom32 + simple menu, there is plenty of

Another week, *another* -pre. I'm really planning on this being the last one. The shortlog is appended below. Apart from a better fix for the "disabled menu entry" bug it's only documentation updates. Testing from the last -pre's has been pretty quiet, so as soon as Ady and Matt have tested this one and confirmed that the disabled entry bug is finally gone I'll do the

I get this error trying to compile current git: nasm -O9999 -f elf -g -F stabs -DDATE_STR="'0x484e9ecd'" \ -DHEXDATE="0x484e9ecd" \ -l pxelinux.lsr -o pxelinux.o pxelinux.asm pxelinux.asm:2693: fatal: unable to open include file `pxeidle.inc' make[1]: *** [pxelinux.o] Fehler 1 - Sebastian

This release includes Murali's menu positioning patch; it is otherwise identical to 2.09-pre13. I will release this as 2.09 on Sunday unless I hear objections. Note that I've effectively been out of the loop, moving houses, for almost a month, so if there is something I'm forgetting please tell me... -hpa

I have pushed out what I hope to be the last release candidate for Syslinux 4.04. Please test it if you have the chance as I would like to have 4.04 out as soon as possible. -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf.

I think we are long overdue for a revision of the header files used in R. This is going to be especially important for a clean build of the CORBA and R/Java stuff which I have been looking over Duncan's shoulder at. It will also let us integrate some of the features Duncan has had to find creative ways around and also to let us integrate things like the PROBLEM buffer problem. I would propose

Hi all, I have looked a bit at what it would take to make the SYSLINUX current directory settable when loading a new configuration file with the CONFIG directive. I have come to the conclusion that it would be a lot less invasive to simply maintain the rule that the current working directory is the one where the config file lives, *including* one loaded via the CONFIG directive. The obvious

I have now officially obsoleted the non-kbuild version of klibc (yes, it's way overdue... my work-for-pay hasn't been too kind to me with time, I'm afraid.) As a result, I've renamed the klibc-kbuild.git repository klibc.git; the old one is now klibc-old.git, but I'm not promising that it will be continued to be maintained going forward. -hpa

I’d like to nominate Quentin Colombet as LSR code owner. He has handled most of the reviews for me for the past couple years (thanks Quentin), and is willing to take on the responsiblity. Frankly, turning over ownership to Quentin is overdue. -Andy

Hello all, I know this question is (strictly speaking) off topic, but if someone could at least point me in the right direction, I would be most grateful. I have an older system (RH 6.2, overdue for upgrade) with an ext2 partition that was pushing 99% filled. I did some space recovery and I have it down to around 90% utilization now. I have rebooted the unit, and brought it up single-user

In a discussion on IRC, Micheal was complaining about the semantics of StringSet, specifically how the iterators work. DannyB mentioned that we have a Trie class, so I decided to check it out. Lo and behold, I couldn't find _any_ uses of it, and when I deleted it from my system and did a clean rebuild, everything was fine. Looking at the log, the last substantial change to this class was in

Hi! I am new to asterisk and I'd like to know wheter the following scenario is possible: Someone press the Button on the door station. The door station dials lets say the extension 333. I take the call on 333 and talk with the person on the door. Now I'd like to activate the door opener by pressing some numbers on the analog telefon. Asterisk should now recognize that I pressed

Dear developers, I don't care for reasons, arguments, or flamefests. I need to plan my workload. By now I have half a dozen servers overdue for reimaging. I can put this off for another week or two, but not really much longer. There's obviously no point in installing centos 5 on any new machine. So I need to know: is there any point in my waiting another week, or should I just say

Hello. I've been testing pxelinux.0 (4.04-pre14) on some laptops: - HP EliteBook 6930P with BIOS F.18. - HP EliteBook 8440P with BIOS F.06. - Dell Latitude E4310 with BIOS A06. When booting pxelinux.0, the machines first display some random letters in different colors and then reboot. We've been using 4.02 for some time without problems. I've tested 4.03 too and it seems to work.