Can I run the newest version of WINE on DragonFlyBSD?

Jonathan Fosburgh syjef at mdanderson.org
Thu Jul 22 12:10:29 PDT 2004


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

On Thursday 22 July 2004 13:24, Justin C. Sherrill wrote:
> MACHINE wrote:
> >  From the link (http://www.winehq.org/?issue=230#Wine%20on%20FreeBSD), I
> > know WINE cannot run well on FreeBSD 4/5 due to VM issue.
> > So what about DragonFly?
>
> [snip]
>
> Jonathan Fosburgh wrote:
> > I'm not sure if the other developers will regard this change
> > favourably, though. They may take the attitude that if Wine can be made
> > to work with the FreeBSD kernel code as is, then Wine should be coded
> > accordingly.
>
> The DragonFly team tends to take a less conservative view than FreeBSD
> core; if you can get this Jonathan Fosburgh fellow to mail
> submit at xxxxxxxxxxxxxxxx with the needed changes, it can get talked about,
> at least.
>
> I haven't run WINE on a DragonFly system myself; I don't know what the
> status is.  Since DragonFly forked from FreeBSD 4.8, Wine may still work
> now if it worked with 4.8.

Um, the above statement was incorrectly attributed to me.  I cannot remember 
who made it, however, and I do not think that anyone actually came up with 
any code.  It was really just a recommendation of what needed to be done to 
make wine work with FreeBSD.  And the current mmap problem with wine should 
be version independent.  It is a relatively new feature of wine.

- -- 
Jonathan Fosburgh
Storage Engineer
UT MD Anderson Cancer Center
Houston, TX 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)

iD8DBQFBABC5qUvQmqp7omYRAm8zAJ4rdpYDdqPlb9Pk2wKd+AckFxF88gCfa+Ag
tyj/PQqotQ5d+iSj0genky0=
=EIj/
-----END PGP SIGNATURE-----






More information about the Kernel mailing list