All the news that fits, we print.
This week, 120 posts consumed 354 K. There were 36 different contributors. 23 (63%) posted more than once. 19 (52%) posted last week too. The top 5 posters of the week were:
|
Wine status page | 19 Jun 2000 00:00:00 -0800 | Archive |
---|---|---|
After Ove Kåven put on line the Wine Status Page, Dmitry Timoshkov asked which metric was used to get the completion percentage for each Wine component (mainly DLLs). Ove replied on the method he uses: There's not much more metric than my own guesstimate or judgement (which I thought would at least be better than no metric), and any corrections the developers would like to tell me about. I didn't try to devise anything complicated... Dimitry also asked whether a todo list could be provided for all the components (so that people could have a look at what remains to be done). Ove liked the idea If developers would like to provide such a list, I could certainly put it online... In a few cases (especially if it's "almost done"), I've tried put a line under the percentage saying what is missing, but I didn't want to spend too much time on it. The discussion then evolved on the completion and remaining parts of Unicode implementation. |
Wine .so files loading | 16 Jun 2000 00:00:00 -0800 | Archive |
---|---|---|
Ove Kåven re-posted a patch (already sent a couple of days ago, and
still not committed to CVS tree) and asked why it has been neither committed nor
rejected. This patch was an attempt to let binary packages for Wine
(like RPM) which normally are installed under /usr/local/wine work out
of the box.
This is a known cause of issues because some Linux distributions
(including Mandrake, Red Hat) no longer include by default /usr/local
in the /etc/ld.conf file (which defines the default directories where
to look for .so files). Since Wine has been highly componentized (and
components are stored in .so files), not founding the Wine .so files
is a brutal case of breakage.
As some of you already now, Wine handles several kinds of components:
|
Wine documentation | 21 Jun 2000 00:00:00 -0800 | Archive |
---|---|---|
John R Sheets wrote:
As part of an effort to improve the accessibility of the Wine
documentation, I've converted (most of) the contents of the
wine/documentation directory into DocBook (an SGML variant).
Naturally, quite a bit of the content is old and crusty, and perhaps
even flat out wrong, but hopefully that can be fixed in the near
future. The docs should be pretty current, including the new OpenGL
docs, and the latest revisions to the wine debugger docs.
The current state of things is sitting at
http://wine.codeweavers.com/docs/
I'm interested in hearing what people think about the organization and
layout. I've done very little proof reading, and only added the bare
minimum of markup to get it up and running ASAP. Quite a lot can be
done to improve the looks; the overall appearance of the generated
HTML is pretty customizable, too.
Later on, John also posted an outline of a possible table of content.
For beginning users; assumes Wine is already installed. Very simple language; task-based.
For all users; includes FTP, CVS, RedHat, Debian, etc. Covers getting it on the system, but not personalizing it.
For the day-to-day user; maintaining Wine on your system. How to configure the basic services, like fonts, printing, multimedia.
For dealing with specific applications.
For developers trying to migrate their apps to UNIX, using Wine.
For developers wanting to contribute to Wine. How to submit patches, what policies to follow, how to debug, and a nice, juicy section on the Wine architecture.
|
Linux networking changes | 21 Jun 2000 00:00:00 -0800 | Archive |
---|---|---|
Berend Ozceri reported: I have a Windows application (Meeting Maker - http://www.meetingmaker6.com) that works fine under the latest Wine (built yesterday from CVS) using Linux kernel version 2.2.14. When I switch to a 2.3.x kernel, the application has networking problems and can't connect to a server. After some analysis by Marcus Meissner and Ove Kåven, it turned out that a specific change in 2.4 kernel series had a nasty side effect: when using the poll function (as the Wine server heavily do for sockets handling), there's a returned valid (POLLHUP) indicating that the connection has hung up. Linux 2.4 changed its behavior and also returned the POLLHUP value for not-yet-connected sockets. As a POLLHUP is currently interpreted in Wine as (only) a closing connection, the effective connection is never seen from Wine. Alexandre Julliard proposed a direction for a fix, which Berend implemented. But this lead to some other issues, meaning that this issue is not over yet. No patch has been provided so far, so be conscious of this pending networking issue on Linux 2.4 (and latest 2.3) kernels for Wine. |
All Kernel Cousin issues and summaries are copyright their original authors, and distributed
under the terms of the
GNU General Public License,
version 2.0.