All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hetz Ben Hamo <hetz@softier.com>
To: qemu-devel@nongnu.org, jm@poure.com
Subject: Re: [Qemu-devel] Fedora Core 2 patch
Date: Thu, 24 Jun 2004 12:31:43 +0300	[thread overview]
Message-ID: <200406241231.43037.hetz@softier.com> (raw)
In-Reply-To: <200406241114.45544.jm@poure.com>

I'm removing the patch for fedora.

The solution is simple. instead of just running qemu and sticking the 
parameters, you should do:

LD_ASSUME_KERNEL=2.2.5 qemu <and the qemu parameters>

Feel free to create an alias in your .bashrc or whatever you favorite shell 
is ;)

I tested it on Fedora Core 2 and in Rawhide - works perfectly OK.

Thanks,
Hetz

On Thursday 24 June 2004 12:14, Jean-Michel POURE wrote:
> Dear all,
>
> I tested again the Fedora patch. The patch does not seem to solve problems,
> unless you are prepared to wait for days before booting up...
>
> Maybe it should be removed from patch repository?
> http://www.dad-answers.com/qemu/patches/Fedora-Core-2/
>
> Fedora Core 2 image can be fetched for testing from:
> http://www.poure.com/qemu/fedora-c2.img.tar.bz2
> http://www.poure.com/qemu/fedora-c2.img.tar.bz2.md5
>
> I read on a mailing-list that the Fedora Core 2 kernel was not compiled
> with GCC and contains some Redhat code as usual.
>
> Testing Fedora Core 2 may simply be a whaste of time...
>
> Cheers,
> Jean-Michel
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel

  reply	other threads:[~2004-06-24  9:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-24  9:14 [Qemu-devel] Fedora Core 2 patch Jean-Michel POURE
2004-06-24  9:31 ` Hetz Ben Hamo [this message]
2004-06-24 10:55   ` Alexander E. Patrakov
2004-06-24 10:26 ` Jean-Michel POURE
2004-06-24 11:53   ` Hetz Ben Hamo
2004-06-24 12:17 ` [Qemu-devel] Fedora Core 2 as guest OS Fabrice Bellard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200406241231.43037.hetz@softier.com \
    --to=hetz@softier.com \
    --cc=jm@poure.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.