similar to: Rsync 3.0.0pre4 released

Hello, I tried to make my own binary with 'make efi64 install' but it fail with make[3]: *** No rule to make target `/root/syslinux-6.02-pre3/efi64/efi/../core//writestr.o', needed by `syslinux.so'. Stop. make[3]: Leaving directory `/root/syslinux-6.02-pre3/efi64/efi' make[2]: *** [install] Error 2 make[2]: Leaving directory `/root/syslinux-6.02-pre3/efi64' make[1]: ***

Hi, I am using qemu for testing new versions of syslinux before installing on an embedded computer. Everything works fine under qemu (1.5.0), so I updated extlinux from 4.06 to 5.11-pre3 on the computer. I found that the autostart's timeout does not work. The timeout value is correct but nothing happens. It worked well with extlinux 4.06... I tried with extlinux 5.01, 5.10, 5.11-pre3 and

On Fri, 28 Jun, at 01:44:56AM, Ady wrote: > 2_ If relevant, fixing the [MENU] INCLUDE directive in 6.xx (which > might be the same fix applied just before the release of 5.11-pre3; I > don't know). Yes, this fix is applicable to the 6.xx releases and will be merged before the final 6.01. -- Matt Fleming, Intel Open Source Technology Center

Le 29/06/2013 12:39, Gene Cumm a ?crit : > On Fri, Jun 28, 2013 at 7:24 AM, Romain Naour <romain.naour at openwide.fr> wrote: >> Hi, >> >> I am using qemu for testing new versions of syslinux before installing on an embedded computer. >> Everything works fine under qemu (1.5.0), so I updated extlinux from 4.06 to 5.11-pre3 on the computer. >> >> I found

> > C_ While initially thought to be a problem with the INCLUDE > > directive, now it seems the problem is the second parameter of the > > CONFIG directive. The second parameter of the CONFIG directive (which > > sets a new CWD) doesn't seem to work correctly (tested with pwd.c32), > > specially when the new cfg file (the first parameter of the CONFIG >

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

I've been working with Matt Burgess here on this problem, and have found the following: syslinux 3.08-pre10 ? broken >>> config.inc:max_cmd_len=255 syslinux 3.08-pre11 ? works >>> config.inc:max_cmd_len=1023 syslinux 3.08 ? works >>> config.inc:max_cmd_len=1023 syslinux 3.09-pre1 ? works >>> config.inc:max_cmd_len=1023 syslinux 3.09-pre2 ? broken

On Fri, 28 Jun, at 10:56:00AM, Helmut Hullen wrote: > Sorry - 5.11-pre3 works well, but 6.01-pre4 (compiled with "make bios") > still has the "include" error. The fix for INCLUDE is in 6.01-pre5. -- Matt Fleming, Intel Open Source Technology Center

I found that the version of isolinux.bin (and the debug version too) doesn't work on my Via C3 system. I get the SAY text, but never the boot: prompt. C-A-Del doesn't reboot either. The debug version does not print anything after announcing it's opening the config file. Only the single SAY text follows. The cursor sits on the next blank line, useless (no responses to key presses).

The ext3-2.4-0.9.17-2418p3 patch applies with 0 fuzz against both 2.4.18 pre 4 and 2.4.18 pre3-ac2. Will it be included into 2.4.18 pre 5? -- Ralf Hildebrandt (Im Auftrag des Referat V A) Ralf.Hildebrandt@charite.de Charite Campus Virchow-Klinikum Tel. +49 (0)30-450 570-155 Referat V A - Kommunikationsnetze - Fax. +49 (0)30-450 570-916 "Debugging is

I upgraded to pre3 a couple hours ago & right now I'm watching my 00:00 backup set absolutely _crawl_. Typically, backups would have been finished somewhere in the 00:10 to 00:30 range, depending how much data changed across 6 machines in the past day. As I write this, the 3rd of 6 machines is (hopefully) just finishing its backup with no more than the usual changes per machine. Whiskey

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

When trying to make the last version I'm getting this error (#./configure --prefix=/some/dir); #make): ============================ gcc -g -O2 -I/usr/local/openssl/include -DPKGLIBDIR=/usr/local/tinc_new/lib /tinc -DCONFDIR=\"/usr/local/tinc_new/etc\" -DLOCALEDIR=\"/usr/local /tinc_new/share/locale\" -DLOCALSTATEDIR=\"/usr/local/tinc_new/var\" -o tincd

I'm stuck behind a corporate NAT that I obviously have absolutely no control over. The nice thing is that the firewall rules, AFAIK, are very nice. I've had tinc running before from behind nazi firewalls with no NAT. Been fiddling with tinc for many hours, but have been SOL. The local machine is the client (has ConnectTo in the conf), and remote is the server (has Listen in the conf).

Can someone suggest anything that will help with the following ext3 performance problem? (It's a Berkeley db issue at bottom, but the ext3 part is worth looking at, I think.) First, two paragraphs of background: A Bayesian spam filter called bogofilter uses Berkeley db to maintain two database files of identical format: one containing words found in spam email and for each word the number

Which version should I use out of the list? Or do I install all of them, one after the other? ext3-2.4-0.9.9-2410p4.gz 05Sep01 (Against 2.4.10-pre4) (Changelog) ext3-2.4-0.9.9-249ac9.gz 05Sep01 (Against 2.4.9-ac9) ext3-2.4-0.9.10-2410.gz 23Sep01 (Against 2.4.10) (Changelog) patch-rml-2.4.10-ac3-ext3-0.9.9-with-dir-speedup-1.gz 01Oct01 (From Robert Love. Unofficial :-))

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,

> > > Short summary: > > I think bug #45 > > http://bugzilla.syslinux.org/show_bug.cgi?id=45 > > "Regression in Syslinux 6.xx. Doesn't 'hand over' to linux kernel" > > can be reproduced using VirtualBox 4.1.x while trying to boot a > > relatively-newish Linux kernel. > > Just to report an update... After confirming that the

I'm trying to pick a kernel for ext3. Looking at the web page (http://www.zip.com.au/~akpm/linux/ext3/), I see little that clues me in to the fact that "most" of ext3 is already in (some|most|all) of the 2.4 series kernels. Am I correct that most of the patches listed on the web page now are actually bug fixes to the existing ext3 code, as opposed to previous patches that actually

HI: i just trying memdisk that comes with syslinux 3.35. i try to load a dos image, which contains ghost verison 8.3 and ghost version 11. both version of ghost hangs when start-up. memdisk that comes with 3.40 pre is ok. and many earlier versions is ok too. i try some parameter like "safeint","raw". but none work. i use memdisk with pxelinux, below is part of my