Date: Mon, 4 Jun 2007 11:34:13 +1000 From: Andrew Reilly <andrew-freebsd@areilly.bpc-users.org> To: "Marc G. Fournier" <scrappy@hub.org> Cc: freebsd-emulation@freebsd.org Subject: Re: Wine 'works very bad' under FreeBSD ... Message-ID: <20070604013413.GA18304@duncan.reilly.home> In-Reply-To: <3ADCDD3D6FF7FB9B690ACE80@ganymede.hub.org> References: <3ADCDD3D6FF7FB9B690ACE80@ganymede.hub.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jun 02, 2007 at 02:01:35AM -0300, Marc G. Fournier wrote: > I'm not out to start a Linux vs FreeBSD discussion here, I'm > only interested in finding out if there is anyone on these > lists that is working 'under the hood' with FreeBSD/wine that > is interested in determining why this software does run under > Linux, but not under FreeBSD ... I'm by no means an expert, but I have used Wine successfully in the past, on an ia32 machine. (My main machines are PPC and amd64 now, so it's not an option for me, so I don't bother to keep track of progress.) The two main problems, which distinguish Wine from all other applications is that in order to successfully emulate Windows it needs to (a) manage one of the segment registers that Windows uses for (I think) thread-local storage differently from the way FreeBSD uses it, and (b) be able to map specific virtual memory address ranges with mmap(). In particular, I believe that Wine needs to be able to map some ranges that FreeBSD maintains for kernel memory, or somthing like that. Both seem to require architectural change in FreeBSD, rather than just code-tweaking in Wine. I don't think that many of the FreeBSD architects need or use Wine, so not much is happening... Cheers, -- Andrew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070604013413.GA18304>