Date: Sun, 15 Aug 1999 16:03:25 +0930 (CST) From: Greg Lewis <glewis@ares.maths.adelaide.edu.au> To: Ford Prefect <fordp@guide.chi.il.us> Cc: freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: SMP and WINE Message-ID: <199908150633.QAA09941@ares.maths.adelaide.edu.au> In-Reply-To: <3.0.3.32.19990814230557.00f46c20@pop.interaccess.com> from Ford Prefect at "Aug 14, 1999 11:05:57 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
> A few weeks ago there was a post about WINE not being able to run on an SMP > system, if I recall -current would allow it at that time, but not -stable. > something about sharing data segments between forked proccess I think. I'm > putting together a SMP system and would like to use WINE. I'm wondering if > there have been any changes to -stable in this area, or if there are any > other tricks to get wine running under an SMP kernel. I think that was probably my post :). I've been following the committers list (cvs-all) and haven't seen any of the necessary changes backported to -stable. I believe that Luoqi Chen's vmspace sharing code is necessary for Wine to work under SMP. This was committed to -current April 27th. There have been a couple of related patches since that (as far as I can tell from the commit logs anyway). Does anyone know if there is an intention to backport these changes to -stable or has the code diverged too far for that to be viable? The alternative is to hunt down all the related patches and backport them oneself. I'd love to see Wine working on our SMP server machine, but I'm not about to run -current on it :). -- Greg Lewis glewis@trc.adelaide.edu.au Computing Officer +61 8 8303 5083 Teletraffic Research Centre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199908150633.QAA09941>