similar to: Mailing list fixed

Hi HPA, Regarding the architecture un-supported system calls, I wrapped them with #ifndef __NR_<foo> .. #endif /* __NR_<foo> */ switches. I have already done that. But you also mentioned that in SYSCALLS.def all these calls should be present and marked with '?'.. Is that right..? Could you please give little more detail about the change you want. Thanks and Regards, Anil On

It seems the mailing list has been broken for several days. It should now be temporarily fixed, but because the fix is temporary I can't promise it won't happen again until the permanent fix is available. Sorry for that. -hpa

On 2/20/19 5:22 PM, H. Peter Anvin via Syslinux wrote: > On 2/18/19 8:56 AM, Ady Ady via Syslinux wrote: >> >> BTW, until very recently, we used to have a "syslinux-commits" mailing >> list (and its archive). >> >> Would it be possible to have "syslinux-commits" back (and its archive)? >> >> IIRC, it was "linked" to the

Hi all, While I was gone I thought a bit about the flame war a few weeks ago and some of the very unpleasant private emails some people decided to send me as a result, most of them demanding that I solve *their* particular problem for them. I wanted to get people's feel for what the policy should be for this mailing list. I have so far tried to limit it to the syslinux loader family

I just found a rather embarrassing bug in PXELINUX -- and what's worse -- I wrote an email about it and killed it off accidentally :-/ It appears PXELINUX doesn't free its internal socket buffers (it has 32 of them) when it gets an error reply from the server, including "file not found." This means it will eventually run out of sockets and "go deaf." This

Hi all, I have set up a mailing list that will track all the commits done to the Syslinux git tree. To subscribe, go to: http://www.zytor.com/mailman/listinfo/syslinux-commits This is not a user-postable list; all the contents is automatically generated commit messages. -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf.

All, Thanks for all your help. Now, I can compile the latest source code base on RedHat 5.5 after update nasm(to 2.09) and binutil(2.17). And *make spotless* before *make* under core/ directory. But with the new pxelinux.0, the PXEClient can not bootup. The error info, No valid file system found! And stuck in there. I think maybe the gcc cause the problem. My gcc version is 4.1.2. Thanks aaron

As far as I know the only thing close to that, is to boot DOS from a floppy image (stored on the CD). The floppy image will contain the CD drivers and hence you can use DOS to access the contents of the CD. The floppy image is usually stored in the "boot sector" of the CD, or if you are using utilities like ISOLINUX, then they can be stored on the CD, and ISOLINUX/memdisk can boot

> We now have a new archive repo at zytor.com. Almost all resources and > communication channels depend on zytor.com being on-line, including the > mailing list itself. > > Please note how the "bounces..." address is still "at zytor.com". > Whether that has any (positive or negative) influence in some case / > support / troubleshooting / configuration,

It seems the mailing list has been broken for several days. It should now be temporarily fixed, but because the fix is temporary I can't promise it won't happen again until the permanent fix is available. Sorry for that. -hpa

Hi all, Recently there has been a flurry of spam to this mailing list. I'm considering switching the list to "subscriber post only" as a result. If you send from and receive to different addresses (like I do, for example), you need to subscribe your send-from address as a "no mail" address. Would people object to this scheme? -hpa

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

Signed-off-by: Paul Bolle <pebolle at tiscali.nl> --- man/extlinux.1 | 6 +++--- man/syslinux.1 | 10 +++------- 2 files changed, 6 insertions(+), 10 deletions(-) diff --git a/man/extlinux.1 b/man/extlinux.1 index 3192122..62bf3b1 100644 --- a/man/extlinux.1 +++ b/man/extlinux.1 @@ -57,8 +57,8 @@ about your system and your BIOS; the vast majority of all problems reported turn out to

Traffic on the klibc list has recently been very low, and unfortunately in the meantime, spam has picked up. I'd like to poll the subscribership again if we should switch to subscriber-post-only to curb the spam. -hpa

fix subject and added warning to patch mail, thanks for review. ----- Forwarded message from "H. Peter Anvin" <hpa at zytor.com> ----- Date: Mon, 29 Mar 2010 15:07:01 -0700 From: "H. Peter Anvin" <hpa at zytor.com> To: maximilian attems <max at stro.at> Cc: Colin Watson <cjwatson at ubuntu.com>, klibc at zytor.com, Herbert Xu <herbert at

I'm thinking I should make a commit robot (like the tip-bot for the Linux kernel) for klibc since development has been picking up again. I could revive the old klibc-cvs mailing list, or make a new one from scratch, or even direct all the commits to the main klibc mailing list. What would people's preference be, here? -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work

I'm wondering if people would think it would be a good thing or bad thing to create a separate mailing list for Syslinux development. We are having a large number of active developers by now, and it would be good to discuss things more explicitly via email, as opposed to IRC, so everyone gets it. However, it's not clear to me if it would be better to just leave it on this mailing list,

Hi,, I wud just like to inform that the previous issue of memdisk not booting compressed images still persists !! The release 2.05 that was supposed to fix this issue dint yet solve the problem !! Please, let me know if more info on the problem is required !! Bye, Jassi >From: syslinux-request at zytor.com >Reply-To: syslinux at zytor.com >To: syslinux at zytor.com >Subject:

On 2/18/19 8:56 AM, Ady Ady via Syslinux wrote: > > BTW, until very recently, we used to have a "syslinux-commits" mailing > list (and its archive). > > Would it be possible to have "syslinux-commits" back (and its archive)? > > IIRC, it was "linked" to the commits published at > > git.zytor.com/syslinux/syslinux.git/ > > but

On 01/02/2014 09:59 PM, Geert Stappers wrote: > Op 2014-01-02 om 15:37 schreef H. Peter Anvin: >> On 01/02/2014 04:09 AM, Ferenc Wagner wrote: >>> >>> Issuing another make after this gave the previous error again: >>> >>> isolinux.asm:1102: error: TIMES value -4 is negative >>> >> >> I just fixed this one... it seems to be a