similar to: [PATCH] /proc/sys/kernel/bootloader_type

i install the wine 1.1.25 but after awhile installation stops and heres some detail in terminal > configure: libcapi20 development files not found, ISDN won't be supported. > configure: libldap (OpenLDAP) development files not found, LDAP won't be supported. > > configure: Finished. Do 'make depend && make' to compile Wine. > > cc -c -I. -I.

This series: 1. Updates the boot protocol to version 2.07 2. Clean up the existing build process, to get rid of tools/build and make the linker do more heavy lifting 3. Make the bzImage payload an ELF file. The bootloader can extract this as a naked ELF file by skipping over boot_params.setup_sects worth of 16-bit setup code. 4. Update the boot_params to 2.07, and update the

This series: 1. Updates the boot protocol to version 2.07 2. Clean up the existing build process, to get rid of tools/build and make the linker do more heavy lifting 3. Make the bzImage payload an ELF file. The bootloader can extract this as a naked ELF file by skipping over boot_params.setup_sects worth of 16-bit setup code. 4. Update the boot_params to 2.07, and update the

[ This patch depends on the cross-architecture ELF cleanup patch. ] This series updates the boot protocol to 2.07 and uses it to implement paravirtual booting. This allows the bootloader to tell the kernel what kind of hardware/pseudo-hardware environment it's coming up under, and the kernel can use the appropriate boot sequence code. Specifically: - Update the boot protocol to 2.07, which

[ This patch depends on the cross-architecture ELF cleanup patch. ] This series updates the boot protocol to 2.07 and uses it to implement paravirtual booting. This allows the bootloader to tell the kernel what kind of hardware/pseudo-hardware environment it's coming up under, and the kernel can use the appropriate boot sequence code. Specifically: - Update the boot protocol to 2.07, which

Hello, I come to you beacause i have something that i dont understand : i m using udev on a debian sid with 2.6.15.1 kernel. I have created an deprecated raid at /dev/md0 when i tried doing mkfs.ext3 /dev/md0 i have got : mke2fs 1.39-WIP (29-Mar-2006) Filesystem label= OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) 4643968 inodes, 9277344 blocks 463867 blocks (5.00%)

Hi all, I am trying to compile Wine 0.9.32 from source on an AMD64 desktop running Red Hat Enterprise Linux 4. I configure as follows: % ./configure --prefix=/home/mfuhrer/sw/linux --with-x --enable-wine64 This works fine. I run make depend, followed by make, and get the following error: % make make[1]: Entering directory `/mnt/io/home/mfuhrer/sw/src/wine-0.9.32/tools' make[1]:

Hi, Does anybody know if RAMI (Ruby Ami) is still functional? And is this still compatible with asterisk 1.8 Best Regards, Arjan Kroon Mobillion BV

Hi Ian, can we push multiboot v2 support for Xen/ARM still into 4.3? It looks like it can coexists with zImage in the same binary - the multiboot structure can be put just behind the zImage header and the code can determine how it has been started: zImage bootloaders clears r0, multiboot one''s would set r0 to the MB magic. I will sketch a patch tomorrow, just wondering if we can have

This series updates the boot protocol to 2.07 and uses it to implement paravirtual booting. This allows the bootloader to tell the kernel what kind of hardware/pseudo-hardware environment it's coming up under, and the kernel can use the appropriate boot sequence code. Specifically: - Update the boot protocol to 2.07, which adds fields to specify the hardware subarchitecture and some

This series updates the boot protocol to 2.07 and uses it to implement paravirtual booting. This allows the bootloader to tell the kernel what kind of hardware/pseudo-hardware environment it's coming up under, and the kernel can use the appropriate boot sequence code. Specifically: - Update the boot protocol to 2.07, which adds fields to specify the hardware subarchitecture and some

This series updates the boot protocol to 2.07 and uses it to implement paravirtual booting. This allows the bootloader to tell the kernel what kind of hardware/pseudo-hardware environment it's coming up under, and the kernel can use the appropriate boot sequence code. Specifically: - Update the boot protocol to 2.07, which adds fields to specify the hardware subarchitecture and some

Hello, I'm using X-web lite in a webpage to connect to one of our asterisk server. But now I have a problem, when you are connected to a voice script the voice will not be heard after a couple of seconds. When you press or say something that the voice will come back for a couple of seconds. When I thy X-Lite (stand-alone version) I had the same problem, but when I turned off the

V1 -> V2: Move kmalloc() before mutex_lock(), suggested by Arjan. file_remove_suid() should be called with i_mutex held, file_update_time() too. So move them after mutex_lock(). Plus, check the return value of kmalloc(). Signed-off-by: WANG Cong <amwang@redhat.com> Cc: Arjan <arjan@infradead.org> Cc: Chris Mason <chris.mason@oracle.com> Cc: Yan Zheng

I''ve addressed all (I think/hope) of the review comments. The main change is to expose the guest virtual platform (e.g. memory layout and interrupt usage etc) to the toolstack via the public interface. This is then used during FDT generation. I have just codified the current defacto standard layout, it''s probably not the best layout but any change can be a separate patch/series.

Hi Xen Developers, I had tested new XenARM for Arndale board that is updated in Anthony''s tree from 2 days ago. I expected that will be working. But, I can not boot Dom0 Kernel. I used kernel and XenARM both are from Xen Wiki(http://wiki.xen.org/wiki/Xen_ARM_with_Virtualization_Extensions/Arndale). It (seems) stopped after "(XEN) Freed 212kB init memory" message. When I

hello List, i am in a situation where i cannot get cdr records for call originated from CLI , i am not able to get when i used application or extension. is there any solution regarding this ,i working since last 3 days onto this. regards Dhaval -------------- next part -------------- An HTML attachment was scrubbed... URL:

start it with asterisk -vvvgc bkw ----- Original Message ----- From: "Arjan" <arjan@inventionz.org> To: <asterisk-users@lists.digium.com> Sent: Sunday, July 11, 2004 12:27 PM Subject: [Asterisk-Users] Asterisk on FreeBSD 4.10 dies > Hi All, > > I'm pretty green to Asterisk. I'm trying to work towards a basic setup > with a couple of Cisco 7960's

Hai, Does anybody have problems with a wrong Connected Line ID with asterisk version 1.6 The following bug was for version 1.4, but I cannot make up if this bug is still in version 1.6 http://forums.digium.com/viewtopic.php?t=7780 In version 1.8 it is possible to change the Connected Line ID, but this isn't the case in version 1.6 Regards, Arjan Kroon Mobillion BV

Upstream commit 4370eec05a88 "arm64: Expand arm64 image header" ended up changing the zImage magic (which was actually the initial branch instructio encoding!). The new header has a proper magic number at a fixed location. Switch Xen itself to using this format. Neither the bootwrapper nor the models care about this header themselves and real bootloaders are not widely used, so now is