Reader Chemisor advances a theory in his journal that a linguistic misunderstanding is at the root of many disagreements over different licensing philosophies, in particular BSD vs. GPL. The argument is that GPL adherents desire the freedom of their code, while those on the BSD side want freedom for their projects. "It is difficult to spend a week on Slashdot without colliding with a GPL advocate. Eager to spread their philosophy, they proselytize to anyone willing to listen, and to many who are not. When they collide with a BSD advocate, such as myself, a heated flamewar usually erupts with each side repeating the same arguments over and over, failing to understand how the other party can be so stupid as to not see the points that appear so obvious and right. These disagreements, as I wish to show in this article, are as much linguistic as they are philosophical, and while the latter side can not be reconciled, the former certainly can, hopefully resulting in a more civil and logical discourse over the matter." Click below for Chemisor's analysis of the linguistic chasm.

Ste sends along the cheery little story of Otto Moerbeek, one of the OpenBSD developers, who recently found and fixed a 33-year-old buffer overflow bug in Yacc. "But if the stack is at maximum size, this will overflow if an entry on the stack is larger than the 16 bytes leeway my malloc allows. In the case of of C++ it is 24 bytes, so a SEGV occurred. Funny thing is that I traced this back to Sixth Edition UNIX, released in 1975."

jschauma writes "Alistair Crooks, president of the NetBSD Foundation, announced recently that it 'has changed its recommended license to be a 2-clause BSD license.' This makes NetBSD even more easily available to a number of organizations and individuals who may have been put off by the advertising or endorsement clauses. See Alistair's email and NetBSD's licensing information for more details."

An anonymous reader writes "The FreeBSD Project has begun the switch of its source code management system from CVS to Subversion. At this point in time, FreeBSD's developers are making changes to the base system in the Subversion repository. We have a replication system in place that exports our work to the legacy CVS tree on a continuous basis. People who are using our extensive CVS based distribution network (including anoncvs, CVSup, cvsweb, ftp) will not be interrupted by our work-in-progress. We are committed to maintaining the existing CVS based distribution system for at least the support lifetime of all existing 'stable' branches. Security and errata patches will continue to be made available in their usual CVS locations."

appelza contributed a link to Tuesday's announcement of the next step toward KDE 4.1: "The KDE Project is proud to announce the first beta release of KDE 4.1. Beta 1 is aimed at testers, community members and enthusiasts in order to identify bugs and regressions, so that 4.1 can fully replace KDE 3 for end users. KDE 4.1 beta 1 is available as binary packages for a wide range of platforms, and as source packages. KDE 4.1 is due for final release in July 2008." I haven't used KDE much for the past few years, but the screenshots of a "grown-up" plasma are enough to make me correct that.

Diomidis Spinellis writes "Earlier today I presented at the 30th International Conference on Software Engineering a research paper comparing the code quality of Linux, Windows (its research kernel distribution), OpenSolaris, and FreeBSD. For the comparison I parsed multiple configurations of these systems (more than ten million lines) and stored the results in four databases, where I could run SQL queries on them. This amounted to 8GB of data, 160 million records. (I've made the databases and the SQL queries available online.) The areas I examined were file organization, code structure, code style, preprocessing, and data organization. To my surprise there was no clear winner or loser, but there were interesting differences in specific areas. As the summary concludes: '..the structure and internal quality attributes of a working, non-trivial software artifact will represent first and foremost the engineering requirements of its construction, with the influence of process being marginal, if any.'"

sproketboy writes with news that a developer named Marc Balmer has recently fixed a bug in a bit of BSD code which is roughly 25 years old. In addition to the OSnews summary, you can read Balmer's comments and a technical description of the bug. "This code will not work as expected when seeking to the second entry of a block where the first has been deleted: seekdir() calls readdir() which happily skips the first entry (it has inode set to zero), and advance to the second entry. When the user now calls readdir() to read the directory entry to which he just seekdir()ed, he does not get the second entry but the third. Much to my surprise I not only found this problem in all other BSDs or BSD derived systems like Mac OS X, but also in very old BSD versions. I first checked 4.4BSD Lite 2, and Otto confirmed it is also in 4.2BSD. The bug has been around for roughly 25 years or more."

An anonymous reader writes "OpenBSD 4.3 is now available! Released today, May 1, 2008, 4.3 introduces many new improvements and upgrades. The complete changelog is here. Torrents can be found here." As usual, this release is accompanied by a song.

An anonymous reader writes "Jeremy White from CodeWeavers has made the announcement that an experimental build of CrossOver Games is now available for PC-BSD users. However, this unsupported edition should also work on FreeBSD or DesktopBSD, allowing users to play Windows games on their desktop. The FreeBSD version of CrossOver Games can be downloaded here (registration required)." From the attached notes: "Remember this is an experimental build! If you are on FreeBSD 6.x, you will need to apply a system patch from http://wiki.freebsd.org/Wine to enable wine to function properly. Users of FreeBSD 7.0 and higher do not need this patch."

Derkjan de Haan writes "I am glad to see progress is being made on the the ability of OpenSolaris to boot from a ZFS filesystem: 'This putback provides the ability to boot the Solaris Operating System from a ZFS root file system on both x86 and SPARC platforms. Full ZFS boot and install support will be available in a subsequent build. Because of the phased putback, we recommend waiting for the full boot and install support rather than attempting to use the ZFS boot features separately.'"