Having it as a loadable module that is essentially private to PC-BSD
(though open source, of course) will lead to questions of why Wine works
in PC-BSD and not FreeBSD. That's fine if your intention is to create
a fork of FreeBSD, but I don't know if that's what you really want.
Kris Moore wrote:
> The thought of a KLD hadn't occured to me actually. We are very close to releasing 1.4RC1 though, so it may be a bit to close to work that out at the moment. Tijl would probably be the one to ask about that though, since he's the one making all this come together :)
> However we will ship with the sys source on our disk 2, patch included. We'll just have to ensure we let users know when they do a csup to re-apply the wine patches manually.
> Sent via BlackBerry by AT&T
> -----Original Message-----
> From: Alfred Perlstein <email@example.com>
> Date: Mon, 20 Aug 2007 02:30:09
> To:Kris Moore <firstname.lastname@example.org>
> Cc:Robert Watson <rwatson@FreeBSD.org>, Scott Long <email@example.com>,Daniel Eischen <deischen@FreeBSD.org>,Tijl Coosemans <firstname.lastname@example.org>, David Xu <davidxu@FreeBSD.org>,email@example.com, Xin LI <firstname.lastname@example.org>,src-committers@FreeBSD.org, cvs-src@FreeBSD.org,cvs-all@FreeBSD.org
> Subject: Re: cvs commit: src/sys/kern kern_thr.c syscalls.master src/sys/sys
> * Kris Moore <email@example.com> [070819 08:50] wrote:
>> Even if you decide to only add this new functionality to FreeBSD 7.x,
>> that's fine with us. Our next release of PC-BSD will be our last based
>> on FreeBSD 6.x before moving to 7. We're committed to shipping with the
>> patch Tijl wrote, since the improvements to Wine with it are night and
>> day. Of course if you roll this into the tree, all the better since I
>> won't have to spend the next 6 months to a year reminding users that
>> when they update world, they have to apply the Wine patch first ;-)
> Kris, I support the patch.
> That said, have you toyed with implementing this as a kld that
> you can ship with your code?