search for: 3.31

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

I've been using syslinux on my own Linux recovery CDs for almost a year now, and in that time I've found it useful to be able to automatically load a 64-bit-capable kernel if the CPU supports it. I'd like to share my efforts and submit this patch for syslinux-3.31. It adds a new config file keyword, 'default64', which overrides the default image if a 64-bit CPU is detected.

CentOS Errata and Security Advisory CESA-2010:0919 php security update for CentOS 4 i386: https://rhn.redhat.com/errata/RHSA-2010-0919.html The following updated file has been uploaded and is currently syncing to the mirrors: i386: updates/i386/RPMS/php-4.3.9-3.31.i386.rpm updates/i386/RPMS/php-devel-4.3.9-3.31.i386.rpm updates/i386/RPMS/php-domxml-4.3.9-3.31.i386.rpm

CentOS Errata and Security Advisory CESA-2010:0919 php security update for CentOS 4 x86_64: https://rhn.redhat.com/errata/RHSA-2010-0919.html The following updated file has been uploaded and is currently syncing to the mirrors: x86_64: updates/x86_64/RPMS/php-4.3.9-3.31.x86_64.rpm updates/x86_64/RPMS/php-devel-4.3.9-3.31.x86_64.rpm updates/x86_64/RPMS/php-domxml-4.3.9-3.31.x86_64.rpm

I have just released SYSLINUX 3.31. It is functionally identical to SYSLINUX 3.31-pre4. Changes in 3.31: * The simple menu system (menu.c32 and vesamenu.c32) now support loading more than one configuration file at a time, using MENU INCLUDE or by specifying multiple filenames. * The MENU COLOR statement can now control the shadowing mode. Changes in

After thinking a bit of the multi-file support in 3.31-pre1, and considering a few users' feedback on the subject, I have made a couple of changes: 1. The dummy filename ~ can be used to mean "the main config file". 2. There is a MENU INCLUDE directive now. -hpa

I have decided to promote SYSLINUX 3.31-pre4 to release candidate status. If it tests out OK, it will become 3.31 some time next week, probably. -hpa

Hi, I've attempted to build 3.31 on RHEL3 but it fails since __DBL_MIN_EXP__ and __DBL_MAX_EXP__ used in com32/lib/math/strtod.c is undefined. I added defines with the values used on RHEL4 (derived from cpp -E -dM < /dev/null) and the build then completes. A quick test did not reveal any ill effects. Is there perhaps a better workaround for this? Another little nit I saw was that

When I build syslinux, I normally do make spotless make but this fails with syslinux-3.31 because of 4 files: ./com32/lib/sys/vesa/.background.o.d ./com32/lib/sys/vesa/.drawtxt.o.d ./com32/lib/sys/vesa/.alphatbl.o.d ./com32/lib/sys/vesa/.initvesa.o.d The .initvesa.o.d has some redhat specific path that does not exist on my system: /usr/lib/gcc/x86_64-redhat-linux/4.1.1/include/stdarg.h If

Hi, I'm using Kubuntu and have a problem with the ISOLINUX CDROM booter with versions used since (K)Ubuntu 7.04. The ISOLINUX booter versions 3.36 and 3.53 do not boot my motherboard. The version shipped with Ubuntu 7.04 is I believe ISOLINUX 3.31 but it displays for such a short time I could be wrong. I'm writing to this mail list in case the original Ubuntu bug report never made it

Hallo sir/madam, I have a Chinese brand Ultrasound unit Ivis 60 model which had issues with booting after power fluctuations here in Congo -Africa. It is using a syslinux 3.31 which is continually giving problem when trying to enter BIOS so that I can install new files available on the usb disk. To enter bios you have to continually press "delete button" when starting the unit but no

Test release; supports loading multiple configuration files at the same time (e.g. to deal with a common layout header) in the simple menu system. Test releases, as always, are at: ftp://ftp.kernel.org/pub/linux/utils/boot/syslinux/Testing/ If you test one, please start with the latest release, since I don't always announce prereleases. -hpa

make spotless fails to remove 4 files: ./com32/lib/sys/vesa/.background.o.d ./com32/lib/sys/vesa/.drawtxt.o.d ./com32/lib/sys/vesa/.alphatbl.o.d ./com32/lib/sys/vesa/.initvesa.o.d This breaks the build since those files require redhat header file locations that don't exist on my system. Now I issue make spotless find . -name '.*.d' -exec rm {} \; make and things work, but I

Hello, I tested some things, and found the following: when the kernel image file is present, but the initrd image is not, ONERROR is not called, and PXELINUX stays in the prompt forever ... Other error scenarios tested okay, a down/unresponding TFTP server can lead to 15-20 minutes delay until all tried filenames timeout out ... Just to let you know :) Andreas -- "The problem is not

On 03/19/2017 10:00 AM, Jonathan Billings wrote: > On Sun, Mar 19, 2017 at 08:32:38AM -0400, Mark Weaver wrote: >> I'm getting things ready to upgrade my aging installation of MySQL >> 5.0.95 on my CentOS 5 LAMP server. With the impending EOL date of 3.31 >> fast approaching my sense of doom and urgency is increasing. > > It isn't clear to me, but are you

Hi everybody. Hardware: Several computers with Asus P/I-P55t2P4S motherboard, CPU Pentium MMX and K6-2/3, 128 to 384 MB RAM, Award 4.51PG Bios, Hard disks from 8 GB to 123.5 GB Realtek 8139D based NICs with PXE Boot-Proms PXELINUX 2.06 / MEMDISK 2.06: - fails to boot Compaq PC-DOS 3.31 PXELINUX 2.08 - succeeds to boot Compaq PC-DOS 3.31 with 0, 1, 2 and 3 hdds installed in

Nice to see the venerable syslinux updated to version 3.35. I did happen to encounter an issue with the latest release though. I performed 'syslinux -f' on a 32MB USB drive and all seemed well...until I tried to boot from it. Error message and drive details below: - - - /error message: SYSLINUX 3.35 2007-01-28 EBIOS Loading Invalid or corrupt kernel image. boot: /bootable USB drive

Hi, With this data.frame: > class(rwl) [1] "data.frame" >rwl 0028002F 0028013F 0028032F 1833 3.39 NA NA 1834 3.09 NA NA 1835 3.05 NA NA 1836 3.31 NA NA 1837 2.26 NA NA > colnames(rwl) [1] "0028002F" "0028013F" "0028032F" Ok.... > colnames(rwl[,1]) NULL why??

Hi, I stumbled on a rather odd problem. A brand new HP Compaq dx2200 computer didn't want to boot up pxelinux+memdisk image. The computer just gave "Disk I/O error" and stopped there. Workaround was rather simple... Just attach regular floppy drive to the motherboard and everything started working fine. I tried with older 2.05 (pxelinux+memdisk) and newer 3.31. Both produced

Hi, I'm hope I'm right here. I'm trying to boot a XEN 3.2.1 via PXEBoot using the following config: LABEL xen_3.2_amd64 kernel mboot.c32 append images/debian/xen_3.2/amd64/xen-3.2-1-amd64.gz \ --- images/debian/xen_3.2/amd64/vmlinuz-2.6.26-bpo.1-xen-amd64 rw root=/dev/nfs nfsroot=172.16.0.1:/var/lib/tftpboot/clientroot panic=0 \ ---