According to section 9 of the GPL, you would only have to contact
contributors for code which specified version 2 of the GPL and not later...
e.g.
* Copyright (c) 2003-2005 Fabrice Bellard
*
* This library is free software; you can redistribute it and/or
* modify it under the terms of the GN
dragoran wrote:
> Bill C. Riemers wrote:
>> You don't need to compile kqemu into the kernel. When I install
>> dkms-kqemu from freshrpms, I do NOT rebuild my kernel. I am fairly
>> certain with Fedora's new policy for extras, there would not be much
>> of
You don't need to compile kqemu into the kernel. When I install dkms-kqemu
from freshrpms, I do NOT rebuild my kernel. I am fairly certain with
Fedora's new policy for extras, there would not be much of a problem getting
it added to Fedora. For that matter, it could probably get added into the
n
I would suggest just the opposite, under commit your ram. If your base operating system is Linux, you can create your swap partitions under a host linux tmpfs directory. You can then safely over commit the amount of tmpfs swap space. The guest linux system will expect he swap to be slow, so it
About a month ago, I used 'fetchmail' to copy mail from an IMAP folder to gmail. I accidently used the wrong flags, and about 100 messages were redelivered... Perhaps someone else has accidently done the same thing with messages from this mailing list?
BillOn 8/21/06, Bruno Abinader <[EMAIL PROT
I was talking to a friend at Red Hat. He says what they suggest using ext3, but putting the journal file small separate internal SCSI drive If you do so you will get far better performance and reliability than from reiserfs.
BillOn 8/7/06, R. Armiento <[EMAIL PROTECTED]> wrote:
Jens Axboe wro
Just to throw in my two cents, I notice that on the namesys website, they claim reiser4 is completely safe in the event of a power failure, while reiserfs 3 still requires some recovery. Apparently in reiser4 they somehow design writes to happen in sequences that create atomic events. So the whol
How about compromising, and making the patch a run time option. Presumably this is only a problem when the virtual machine is not properly shutdown. For those ho want the extra security of knowing the data will be written regardless of the shutdown status they can enable the flag. By default it
It seems to me you missed the most important qemu feature. That is qemu will emulate different processors. Just try running an PPC version of Linux on an x86 with VMWARE. To my knowledge the only other programs that can do this are either very expensive or extremely slow.
BillOn 7/28/06, Udo 'Ro
e in
qemu-0.8.1 version. It has nothing to do with recompiling glibc, or downloading different kernel source, or any other such non-sense.BillOn 7/17/06,
Damien Mascord <[EMAIL PROTECTED]> wrote:
Bill C. Riemers wrote:> Good guess, SuSE makes many modifications to the standard kernel. H
Good guess, SuSE makes many modifications to the standard kernel. However, the kernel source is not the problem. I downloaded fresh kernel source from www.kernel.org, and I still have the exact same error. Here are the relevant details:
QEMU version: qemu-0.8.1Linux Kernel: 2.6.16.13Operating Sy
11 matches
Mail list logo
