Wine 'works very bad' under FreeBSD ...

Marc G. Fournier scrappy at hub.org
Wed Jun 27 17:10:27 UTC 2007


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



- --On Monday, June 04, 2007 11:34:13 +1000 Andrew Reilly 
<andrew-freebsd at areilly.bpc-users.org> wrote:


> 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...

Please see <http://wiki.freebsd.org/Wine> ... we've addressed the 'Wine loader' 
issue you comment on above, from the Wine side of things ... we've also 
addressed several other issues from both the FreeBSD and Wine sides, as 
appropriate ...

- ----
Marc G. Fournier           Hub.Org Networking Services (http://www.hub.org)
Email . scrappy at hub.org                              MSN . scrappy at hub.org
Yahoo . yscrappy               Skype: hub.org        ICQ . 7615664
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (FreeBSD)

iD8DBQFGgpoB4QvfyHIvDvMRAnk9AJwO0sUGNAYwKD+OAkkB8qt6XvXe5gCgwLKS
/nVVpAOrhZcKkE6Qz9hNlfk=
=pHGn
-----END PGP SIGNATURE-----



More information about the freebsd-emulation mailing list