Linux blog writes "The new version of OpenBSD is available for download. There are lots of nifty new features to try out including OpenSSH 5.1 with chroot(2) support, Xenocara, Gnome 2.20.3, KDE 3.5.8, etc. Machines using the UltraSPARC IV/T1/T2 and Fujitsu SPARC64-V/VI/VII are now supported. It seems amazing to me that they keep delivering these new results on a six-month release cycle."

Read more of this story at Slashdot.

The call of ktulu writes "Good things come to those who wait. After eight months of work the relatively new project BSDanywhere has announced its first final release 4.3. BSDanywhere is a bootable Live-CD image based on OpenBSD. It consists of the entire OpenBSD base system (without compiler) plus enlightenment desktop, an unrepresentative collection of software, automatic hardware detection and support for many graphics cards, sound cards, SCSI and USB devices as well as other peripherals. Give it a spin."

Read more of this story at Slashdot.

thhamm writes "The GNOME community hopes to make our users happy with many new features and improvements, as well as the huge number of bug fixes that are shipped in this latest GNOME release! Well. What else to say. I am happy." Notably, this release is also the occasion for the announcement of videoconferencing app Ekiga's 3.0 release.

Read more of this story at Slashdot.

Gonzalo Martinez-Sanjuan Sanchez writes "The PC-BSD team is pleased to announce PC-BSD version 7.0! (Release Name: Fibonacci Edition.) This release marks a milestone for PC-BSD, by moving to the latest FreeBSD 7-Stable and also incorporating the KDE 4.1.1 desktop. Users will immediately notice the improved visual interface that KDE 4.1.1 offers, as well as a large improvement in hardware support and speed from the update to FreeBSD 7-Stable."

Read more of this story at Slashdot.

StoneLion writes "After months of development and controversy, the KDE project announced the release of KDE 4.1 today. Linux.com (a Slashdot sister site) took a hands-on look at the new code, and reviewer Jeremy LaCroix says, 'KDE 4.1 simply rocks.'" Bruce Byfield's review is quite positive, as well.

Read more of this story at Slashdot.

andrewmin writes "Recently, Gnome's been gaining a lot of ground on its KDE counterpart in the desktop environment wars. The KDE developers were hoping to change this with KDE 4, the new radical release of KDE, but it was not to be. KDE 4.0 was buggy and unstable, leaving everyone except the hard-core KDE lovers. Mainly, this was because it just didn't work most of the time. However, the developers were not without hope. They promised that KDE 4.1 would be more stable and fix all the holes and problems with KDE 4.0. That time is coming soon: in just four days, K Desktop Environment 4.1 will be released to the Linux masses." A release candidate for 4.1 came out just over a week ago, with binaries available "for some Linux distributions, and Mac OS X and Windows."

Read more of this story at Slashdot.

An anonymous reader writes "DragonFly BSD 2.0 has been released! It includes HAMMER, DragonFly's brand-new file system supporting advanced features like history, snapshots and various other cool things. Will it become the new ZFS? Since it is BSD licensed it could also be integrated into various other operating systems."

Read more of this story at Slashdot.

benuski writes "Today at GUADEC, the Gnome User and Developer European Conference, the gtk+ team announced their plans for gtk+ 3.0; immediately after, the Gnome release team announced their plans for Gnome 2.30 to be changed into Gnome 3.0. This would mean a release date a year and a half to a year in the future. Details are short at the moment, but the Gnome team seems to be following in KDE's footsteps, but hopefully will avoid the problems that plagued KDE 4.0's release."

Read more of this story at Slashdot.

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.

Read more of this story at Slashdot.

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."

Read more of this story at Slashdot.

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."

Read more of this story at Slashdot.

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."

Read more of this story at Slashdot.

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.

Read more of this story at Slashdot.

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.'"

Read more of this story at Slashdot.

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."

Read more of this story at Slashdot.