From: Adam Jackson a...@redhat.com
vm86 has been defaulted off since 1.6, and is still a terrible idea to
actually use. Time to say goodbye.
The stub backend is only ever built by default on freebsd/ppc, and can't
be doing any good there. The right fix is --disable-int10 if you want
to not
On Wed, Sep 14, 2011 at 12:25:20 -0500, Jamey Sharp wrote:
From: Adam Jackson a...@redhat.com
vm86 has been defaulted off since 1.6, and is still a terrible idea to
actually use. Time to say goodbye.
The stub backend is only ever built by default on freebsd/ppc, and can't
be doing any
On Wed, Sep 14, 2011 at 12:25:20PM -0500, Jamey Sharp wrote:
From: Adam Jackson a...@redhat.com
vm86 has been defaulted off since 1.6, and is still a terrible idea to
actually use. Time to say goodbye.
Not a good idea. I've reenabled it in our enterprise product lately.
Reason: I've run
On Wed, 2011-09-14 at 19:28 +, Egbert Eich wrote:
On Wed, Sep 14, 2011 at 12:25:20PM -0500, Jamey Sharp wrote:
From: Adam Jackson a...@redhat.com
vm86 has been defaulted off since 1.6, and is still a terrible idea to
actually use. Time to say goodbye.
Not a good idea. I've
On Thu, 29 Jul 2010 13:53:39 -0400, Adam Jackson a...@nwnk.net wrote:
On Wed, 2010-07-28 at 11:35 -0400, Alex Deucher wrote:
On Wed, Jul 28, 2010 at 11:29 AM, Alan Coopersmith
alan.coopersm...@oracle.com wrote:
Isn't vm86 even further limited to just those machines running the Linux
On Wed, 2010-07-28 at 11:35 -0400, Alex Deucher wrote:
On Wed, Jul 28, 2010 at 11:29 AM, Alan Coopersmith
alan.coopersm...@oracle.com wrote:
Isn't vm86 even further limited to just those machines running the Linux
kernel, not BSD or Solaris or anything else? (Okay, maybe that doesn't
On Tue, Jul 27, 2010 at 08:23:05PM +0200, Mark Kettenis wrote:
How about fixing those bugs before killing it?
Because right now there's no incentive for anyone to fix those bugs
because they can use the vm86 backend instead?
--
Matthew Garrett | mj...@srcf.ucam.org
Matthew Garrett wrote:
On Tue, Jul 27, 2010 at 10:47:05PM +0200, Mark Kettenis wrote:
Which makes me seriously doubt that these bugs can be found and fixed
fast enough such that users won't be affected.
If vm86 were an option on anything other than 32-bit x86 I'd have
sympathy with
On Wed, Jul 28, 2010 at 11:29 AM, Alan Coopersmith
alan.coopersm...@oracle.com wrote:
Matthew Garrett wrote:
On Tue, Jul 27, 2010 at 10:47:05PM +0200, Mark Kettenis wrote:
Which makes me seriously doubt that these bugs can be found and fixed
fast enough such that users won't be affected.
If
On Wed, Jul 28, 2010 at 08:29:50AM -0700, Alan Coopersmith wrote:
Isn't vm86 even further limited to just those machines running the Linux
kernel, not BSD or Solaris or anything else? (Okay, maybe that doesn't
take a huge chunk out of the number of machines that can run it, but it
is
Date: Tue, 27 Jul 2010 17:57:01 +0100
From: Matthew Garrett m...@redhat.com
On Wed, Jul 14, 2010 at 04:15:56PM +0300, Tiago Vignatti wrote:
On Tue, Jul 13, 2010 at 11:32:54PM +0200, ext Adam Jackson wrote:
vm86 has been defaulted off since 1.6, and is still a terrible idea to
actually
From: Adam Jackson a...@redhat.com
Date: Tue, 27 Jul 2010 15:46:59 -0400
On Tue, 2010-07-27 at 20:23 +0200, Mark Kettenis wrote:
Date: Tue, 27 Jul 2010 17:57:01 +0100
From: Matthew Garrett m...@redhat.com
On Wed, Jul 14, 2010 at 04:15:56PM +0300, Tiago Vignatti wrote:
On Tue, Jul
On Tue, 2010-07-27 at 22:47 +0200, Mark Kettenis wrote:
From: Adam Jackson a...@redhat.com
Some of them are... nontrivial.
Which makes me seriously doubt that these bugs can be found and fixed
fast enough such that users won't be affected.
Perhaps they can consider running an older X
Hi!
On Tue, Jul 13, 2010 at 11:32:54PM +0200, ext Adam Jackson wrote:
vm86 has been defaulted off since 1.6, and is still a terrible idea to
actually use. Time to say goodbye.
My empirical evidences say that we can't do this.
I had different behaviour running some systems with x86emu and
vm86 has been defaulted off since 1.6, and is still a terrible idea to
actually use. Time to say goodbye.
The stub backend is only ever built by default on freebsd/ppc, and can't
be doing any good there. The right fix is --disable-int10 if you want
to not ship int10 support.
Signed-off-by:
15 matches
Mail list logo