All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steffen Sledz <sledz@dresearch.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Ugly build problem with emacs/qemu
Date: Sat, 07 Mar 2009 13:37:32 +0100	[thread overview]
Message-ID: <49B26A8C.7090301@dresearch.de> (raw)
In-Reply-To: <200903062024.13519.marcin@juszkiewicz.com.pl>

Am 06.03.2009 20:24, schrieb Marcin Juszkiewicz:
> On Friday 06 of March 2009 19:47:58 Justin Patrin wrote:
>>> I don't kow about openSuse, but I remember that Fedora used to have
>>>   some kernel patches that did not play well with QEMU. But that was
>>>   back on Ferora 7, since then I switched to ubuntu. I don't even
>>>   rmember exactly what patch caused the problems, but IIRC it was
>>>   security related.
>> Hmmm, good point it could be SELinux. Could you try disabling that,
>> if you have it enabled?
>
> It is not SELinux but one kernel patch - linux-2.6-execshield.patch to
> be exact. Rebuild Fedora kernel without that one or use vanilla one.
>
> Took me lot of kernel rebuilds to find that out.

I've no SELinux running and i've tried the vanilla kernel. But the problem's still there. :(

# uname -a
Linux mobil-400-300 2.6.27.19-3.2-vanilla #1 SMP 2009-02-25 15:40:44 +0100 i686 i686 i386 GNU/Linux

Steffen



  parent reply	other threads:[~2009-03-07 12:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-19  8:21 Ugly build problem with emacs/qemu Sledz, Steffen
     [not found] ` <49A7BD17.2080407@dresearch.de>
2009-02-27 20:28   ` Justin Patrin
2009-03-01 15:11     ` Steffen Sledz
2009-03-02 17:42       ` Hans Henry von Tresckow
2009-03-06 18:47         ` Justin Patrin
2009-03-06 19:24           ` Marcin Juszkiewicz
2009-03-06 20:28             ` GNUtoo
2009-03-07 12:37             ` Steffen Sledz [this message]
2009-03-06 20:27           ` GNUtoo

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=49B26A8C.7090301@dresearch.de \
    --to=sledz@dresearch.de \
    --cc=openembedded-devel@lists.openembedded.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.