-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
- --On Saturday, June 02, 2007 10:55:00 +0200 Kai Blin kai.blin@gmail.com wrote:
Right. And it's not as if we didn't try. Just two days ago, I've sent the following email to the freebsd-hackers mailing list: http://lists.freebsd.org/pipermail/freebsd-hackers/2007-May/020761.html
So far I've received one response, telling me to contact the ports maintainer. I haven't followed up on this yet, but being a maintainer for a couple of RPMs myself, I know that just being the maintainer doesn't mean I know how to fix the source code of the package I maintain. I was kind of hoping for some FreeBSD developers who know the memory management of their OS to at least offer some pointers on where to look. Didn't happen so far.
As I said in my email, I'm really happy to provide the Wine side of things for this bug, but I don't feel like doing the FreeBSD research. I don't use FreeBSD and my time is limited.
S'alright, I don't mind working from the FreeBSD side of things, as long as I'm not hitting a 'Linux vs FreeBSD' wall trying to do it :) Why I run FreeBSD is my choice, why you run Linux is yours ... IMHO, neither of us are running Windows, which should be all that truly matters :)
Let me read through your email and see if I can nudge some comments out of some of the 'kernel developers' that I know, who might be able to help shed some light ... or at least get us moving forward ...
- ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664