similar to: default64 patch?

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.

Author: ultrotter Date: 2006-02-19 18:38:10 +0000 (Sun, 19 Feb 2006) New Revision: 26 Added: trunk/debian/patches/30xenchangeset.dpatch Modified: trunk/debian/patches/00list trunk/debian/patches/10sysconfig.dpatch trunk/debian/rules Log: Add 10sysconfig.dpatch description Add 30xenchangeset.dpatch to make the xen changeset configurable Force the xen changeset to be the correct one

From: Wei Yongjun <yongjun_wei at trendmicro.com.cn> Add the missing unlock before return from function fill_balloon() in the error handling case. Introduced by 9864a8(virtio_balloon: introduce migration primitives to balloon pages) dpatch engine is used to auto generate this patch. (https://github.com/weiyj/dpatch) Signed-off-by: Wei Yongjun <yongjun_wei at trendmicro.com.cn> ---

From: Wei Yongjun <yongjun_wei at trendmicro.com.cn> Add the missing unlock before return from function fill_balloon() in the error handling case. Introduced by 9864a8(virtio_balloon: introduce migration primitives to balloon pages) dpatch engine is used to auto generate this patch. (https://github.com/weiyj/dpatch) Signed-off-by: Wei Yongjun <yongjun_wei at trendmicro.com.cn> ---

The following is a pxelinux problem, specifically to do with including config files with the menu include directive and the ifcpu64.c32 com module. I have a working ifcpu64.c32 setup that jumps to the label rescue64 in the case of a 64-bit CPU. The label "rescue64" defines a 64-bit kernel and a 64-bit initrd.img. The setup jumps to a label named "rescue32" in the case of a

Hallo, if I try to PXE-boot a debian/ubuntu/clonezilla/debianlike live CD (with a directory "live", just for recognising this type) via LABEL clonezilla MENU LABEL ^Clonezilla (iso) kernel memdisk append iso initrd iso/clonezilla.iso that doesn't work: This Debian Live image failed to boot. ... ... The error message was Unable to find a medium containing a

Hello, as said in the subject; I am having problems with ifcpu.c32 and ifcpu64.c32 detecting a Athlon II X4 CPU correctly as a 64Bit capable CPU. Ifcpu64.c32 does not detect PAE capabilities, also. Both boot the last (32Bit, non-PAE) entry. On two other Core2-based machines I have here, everything works. Can someone tell me what exactly these modules are looking for? Maybe I can compare that

THE GOOD: NUT is able to communicate with my Powerware 5115A over USB using the bcmxcp_usb driver: ambient.temperature: 38 battery.charge: 99 battery.runtime: 9000 battery.voltage: 27.07 driver.name: bcmxcp_usb driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.version: 2.2.1 driver.version.internal: 0.13 input.frequency: 50.34 input.voltage: 235 output.current: 0.0

The default path is /var/run/tftpd-hpa.pid, which can be overridden by the newly introduced -P option. On normal termination (SIGTERM or SIGINT) the pid file is automatically removed. Moved setting the umask later, right before entering the select loop, so that it does not affect the permissions of the pid file. Signed-off-by: Ferenc Wagner <wferi at niif.hu> --- tftpd/tftpd.c | 38

Hi I'm trying to build an Asterisk packages for a C3 system (256MB memory, cpuinfo below). /proc/cpuinfo: processor : 0 vendor_id : CentaurHauls cpu family : 6 model : 9 model name : VIA Nehemiah stepping : 8 cpu MHz : 1000.736 cache size : 64 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu

Hello all, I'm thinking about wrapping up a 3.70 release, even though gpxelinux.0 is technically not feature-complete. I'd like people's opinion on it. -hpa

Hi, during the week I was thinking to send an email to the upstream development list to see if, at some point in the future, we might have the changes needed for us not to patch their package, or to reduce our patches even more... The points I was going to touch were: /etc/sysconfig: We'd like, if it's possible, to have this be configurable at build time... The default can remain like

On Wed, Oct 30, 2013 at 09:52:57AM +0200, Ady wrote: > > > The wiki (http://www.syslinux.org/wiki/index.php/PXELINUX) still says: > > > > "copy pxelinux.0 (from the SYSLINUX distribution) and any > > kernel or initrd images that you want to boot" > > > > like I've been doing forever, but how do I know what else I need, and > >

I've been working on a buildrelease.sh script to call hg2dist.sh, export debian/ from svn and run dpkg-source for me. When I ran dpkg-source I noticed that it gave warnings regarding the *.dpatch files being chmod 0755 is there any reason to maintain this within the repository or would 0644 suffice and remove these warnings from dpkg-source? Regards, Jeremy --

Hello everyone, Since I have some some adventures in UEFI PXE booting ahead I tried to go with the latest syslinux development snapshot in this case 5.10pre1. But I already fail when booting from CD with Failed to load COM32 file .c32 I am a bit perplex since no name of COM32 files is given. I am trying to trace down the issue as good as I can. COM32 files present are:

Dear syslinux list members, I'm a newbie on this list. I hope I don't offend anyone by being slightly off-topic. I had the problem of wanting multiple Linux distros (i.c. Debian, Ubuntu, OpenSuSE, SuSE, RedHat, CentOS, Fedora) installable from a single PXELinux menu, so I wrote a couple of scripts that do what is described below. The question is whether anyone would be interested in

Tags: patch, upstream Hi, when configuring nut 2.2.0 the variable/symbol `@SSL_LDFLAGS@' is not resolved by the libupsclient-config script. The attached patch changes `@SSL_CFLAGS@' to `@LIBSSL_CFLAGS@' `@SSL_LDFLAGS@' to `@LIBSSL_LDFLAGS@' which should solve this issue. Regards, -octo -- Florian octo Forster Hacker in training GnuPG: 0x91523C3D http://verplant.org/

Given an isohybrid image, I'd like default to a different label when booted from usb vs. when booted from cd. Is there a way to do accomplish this, something similar to ifcpu64.c32 perhaps? Thanks. Joe

Mattias Schlenker <ms at mattiasschlenker.de> wrote: > Is ifcpu.c32 or ifcpu64.c32 sufficient for your task? No. I need to detect a given machine by something unique. E.g. the MAC-address of the Ethernet Interface CPU-id or such, because I have custom kernels for all the machines. Sven -- If you can spend five minutes on the Internet and do not run Linux, you're a genius. (Dirk

We are running * V1.0.9 on a demo box. We have set up everything in our dialplan and we have a directory where we store individual extension settings. That directory is called "extensions-phones.d" and it contains a number of .conf files. In my extensions.conf file I have put a #include "extensions-phones.d/*.conf" in my [globals] context If we reload and restart *, and