similar to: syslinux-3.36-pre8 feedback

I have tested with 3.31 (does not broke /dev/null) and 3.35/3.36 that broke /dev/null I verify that /dev/null exist, then compile one of the target available on top Makefile and /dev/null no more exist. Example root:/usr/src/syslinux-3.36# cat /dev/null root:/usr/src/syslinux-3.36# make .depend Makefile:274: .depend: No such file or directory rm -f .depend for csrc in syslxmod.c gethostip.c ; do

I made a patch that depending of gcc flavor add -no-pie or -nopie on libutil and dos Makefile. This fix fatal error like this sha1hash.c: In function `SHA1Transform': ../include/netinet/in.h:24: error: can't find a register in class `BREG' while reloading `asm' ../include/netinet/in.h:24: error: can't find a register in class `BREG' while reloading `asm'

Signed-off-by: Gilles Espinasse <g.esp at free.fr> --- scripts/Makefile.host | 2 +- usr/klibc/CAVEATS | 2 +- usr/klibc/README.klibc | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/scripts/Makefile.host b/scripts/Makefile.host index d8ab687..6a6b949 100644 --- a/scripts/Makefile.host +++ b/scripts/Makefile.host @@ -5,7 +5,7 @@ # # Both C and C++ is

We used syslinux package on IPCop with success to install from floppy, from cdrom, from usb key and pxe. I upgrade the distribution nine month ago from 2.11 to more recent versions (3.11, later 3.20). We add one consistent report of a laptop machine that boot with 2.11 but fail with 3.11 and 3.20 Symptom is that the machine don't display anything after loading the kernel and initrd. with

Is it possible to configure syslinux.cfg on a floppy to start Win98 on a secondary hard drive? If so, how is this done? Currently I have Linux and Win98 on the primary hard drive, and when I attempt to use the floppy to start Win98 on the second hard drive, I simply start Win98 on the first drive. I have tried many different approaches, all to no avail, and I would really appreciate some

Trying to be not long, on x86 I have 3 floppies images boot, root-1, root-2 Booting from boot image with no problem, I try reading root-1 and root-2 image in raw format. Reading root-1 and root-2 is made from boot init script, using klibc-1.5.9 or klibc-1.5.10 with debian insmod patch, and a vanilia linux-2.6.24.7 root-1 and 2 images are smaller than 1440 kB and are made the same way with cd

I have seen it's been planned to change the default file name to be shorted than module.pcimap. One way to solve the longer than 8.3 name issue should be to recommend using mkisofs -J -r But is not module.pcimap going to disappear? Should HDT not parse module.alias instead? An option has been added on module-init-tools to remove generation of all module.*map files. Default behavior is still

Signed-off-by: Gilles Espinasse <g.esp at free.fr> --- gpxe/src/Makefile.housekeeping | 10 ++++++++++ 1 files changed, 10 insertions(+), 0 deletions(-) diff --git a/gpxe/src/Makefile.housekeeping b/gpxe/src/Makefile.housekeeping index 1f5e115..d49416e 100644 --- a/gpxe/src/Makefile.housekeeping +++ b/gpxe/src/Makefile.housekeeping @@ -134,6 +134,16 @@ SP_FLAGS := $(shell $(SP_TEST)

gcc hardened by default is seen on gentoo, alt-linux, HLFS, etc. Patch fix on syslinux this error during gpxe compilation: [BUILD] bin/cpu.o arch/i386/core/cpu.c: In function 'get_cpuinfo': arch/i386/include/bits/cpu.h:79: error: can't find a register in class 'BREG' while reloading 'asm' arch/i386/include/bits/cpu.h:79: error: can't find a register in class

Hi All, A colleague of mine is using syslinux-3.20-pre8, syslinux.com, under DOS to install syslinux loader. It gives "sector read error". He re-compiled syslinux.com under a linux box, and used it successfully to install the loader from DOS. He is installing it on a hard drive (C:) He booted from a floppy and ran: "syslinux.com C:" at A:\ prompt He tried with

Am I wrong saying that actually anyone that use klibc has to use insmod patch or build a monolithic kernel? Could not the insmod patch be include? That will make everyone life easier on klibc upgrade. Gilles

Is there a list of which kernel versions (are supposed to) work with (each version of) klibc? I do recall reading something that said klibc should run under any version of the kernel, regardless of which version it is compiled against. Following the new instructions on this list earlier (to use the KLIBCKERNELSRC= parameter to point to the installed kernel headers) as well as also making the

Hello, are there known issues with some bioses not booting from Superfloppy format? All I get is the Syslinux (c) line and nothing else happens afterwords. Everything works fine if a partition is added to the device. Unfortunately however the target device can not be partitioned. Any hint? Sven -- Why are there so many Unix-haters-handbooks and not even one Microsoft-Windows-haters

Compilation was ok with klibc-1.5.10 on linux-2.6.25. Distrib does not matter as it is inside a chroot a la LSF With the upgrade to linux-2.6.27 it broke on 1.5.10 (I try too the last 1.5.14) with make[1]: Entering directory `/usr/src/klibc-1.5.14' GEN klcc/klibc.config GEN klcc/klcc HOSTCC scripts/basic/fixdep KLIBCCC usr/klibc/__static_init.o KLIBCCC usr/klibc/vsnprintf.o

I have, hopefully, found and fixed the issue with non-kernel binaries that appeared in 3.35. As a result, I have pushed out 3.36-pre6 and am classifying it as a release candidate. Please try it out, especially if you have had problems with 3.35. ftp://ftp.kernel.org/pub/linux/utils/boot/syslinux/Testing/ -hpa

At first I thought, I was dealing with the known EBIOS/CBIOS-problem. The symptom was exactly the same (hangs at ...EBIOS). As 3.10-pre8 and 3.10-pre9, in contrary what was mentioned in the ML, did not bring any improvement, I looked deeper into what could be my specific problem. I found out that the program just halted at 'cmp [esi],edx' (line 658; ldlinux.asm 3.10-pre9)! By replacing

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

Hi, I am trying to build syslinux-5.11-pre8 but it will fail: /tmp/foo # cat /etc/debian_version jessie/sid /tmp/foo # pwd /tmp/foo /tmp/foo # git clone git://git.kernel.org/pub/scm/boot/syslinux/syslinux.git Cloning into 'syslinux'... remote: Counting objects: 47602, done. remote: Compressing objects: 100% (12273/12273), done. remote: Total 47602 (delta 35454), reused 46954 (delta

I have released SYSLINUX 3.11-pre8; this is a release candidate. The differences versus -pre6 is that I have reverted the PXELINUX stack changes I did in SYSLINUX 3.10 since there are confirmed reports that they break at least one platform. As before, I hope to release 3.11 on Tuesday unless I get objections. ftp://ftp.kernel.org/pub/linux/utils/boot/syslinux/Testing/ -hpa

I have just pushed out SYSLINUX 3.70-pre8. The two main differences is that I have updated the gPXE source base, and added a sanboot module (sanboot.c32). sanboot.c32 *should* be capable of initiating an iSCSI or AoE boot, but I haven't actually tested it. The other main difference is that gPXE now advertises HTTP/1.0 instead of HTTP/1.1, since the code was not actually HTTP/1.1