Jem Matzan's The Jem Report
is running a so-called editorial by Radu-Cristian Fotescu (aka. Béranger
) titled The sorry state of open source today
. I say so-called, because it is more of a rant than an editorial: 26 pages long and not entirely coherent.
I won't waste your time with a point-by-point rebuttal of this piece, not least because most of what he writes is pure opinion and interpretation. I don't necessarily agree with it—I find him a little too radical and a little too confrontational—but he's entitled to it.
(I do agree with his views on the differences between the GPL and the BSD license, but that's neither here nor there)
What I take exception to are factual errors in his discussion of *BSD, and specifically of FreeBSD
First, on page 7
, he writes:
[members of] the *BSD family [are] either backed by 501(c)(3) non-profit organizations like The FreeBSD Foundation or the NetBSD Project, or the task of individuals like Theo de Raadt for OpenBSD and Matt Dillon for DragonFly BSD
This is inaccurate as far as FreeBSD goes. The FreeBSD Foundation
was established because a recognized legal entity (which the FreeBSD Project itself is not) was required for three purposes:
The Foundation contributes to the Project in the sense that it owns some of the hardware that the Project uses, organizes and funds events such as the Developer Summits, which are held twice a year at BSDCan
, and occasionally funds development work.
This does not mean that the FreeBSD Project is backed by the FreeBSD Foundation. The Foundation does not control the Project in any way; it does not control the Project's servers and repositories, it does not approve new committers, write roadmaps or schedule releases. The democratically elected Core Team
This also invalidates the following quote from page 3
even the FreeBSD foundation [sic] is an American subject
The implication is that since the FreeBSD Foundation is subject to American law, the FreeBSD Project is subject to American software patents.
Once again, the Foundation does not control FreeBSD. Moreover, the bulk of FreeBSD development today—at least the cutting-edge work—happens in Europe (especially Eastern Europe, but there are also strong contingents in Denmark, Italy and the UK) and Asia.
situation is different, as The NetBSD Foundation, Inc.
appoints the NetBSD Core Group
and various executive committees
, and handles applications from new developers, who must sign a membership agreement with the Foundation before obtaining write access to the repositories.
The next objection I have relates to the following quotes from pages 10
Maybe the first sign was when FreeBSD tried to mimic Linux and to be "more user-friendly". It was rather wrong, and I can only hope they realized the mistake. The gradual recovery of the once legendary FreeBSD stability can be seen with 6.1 and 6.2. Hopefully the trend will not be reversed again.
Unfortunately, starting with 5.0, the quality and stability of FreeBSD have deteriorated, or maybe it was my hardware that was less supported. Compromises have been made to match the popularity of Linux, and the price to pay was rather high.
These two paragraphs are based on a completely incorrect understanding of what happened between FreeBSD 4 and FreeBSD 6. User friendliness, popularity, Linux envy: none of this ever played any part. I will attempt to briefly explain what actually happened.
FreeBSD first gained support for symmetric multiprocessing in 3.0. The approach chosen then was a simplistic one: the entire kernel was serialized under a so-called "giant lock". This saved a lot of work, as there was no need to make the various kernel subsystems reentrant. It also meant that FreeBSD's SMP performance was not very good, except for computationally intensive tasks (i.e. tasks which did not involve the kernel much), but it was better than nothing.
After FreeBSD 4 was released, work was started on a project called SMPng
, which would replace the giant lock with a number of fine-grained locks, allowing separate kernel threads to run simultaneously on separate processors, performing separate tasks.
This is where two important mistakes were made.
Firstly, the release schedule was feature-bound rather then time-bound. This meant that FreeBSD 5 would be released "when it was done", not "when it was time". Consequently, there was no deadline for developers to focus on, and little effort was made to partition work into manageable pieces to avoid having the source tree in an unreleasable state for long periods of time.
Secondly, and most importantly, it was decided very early on to go for a complicated M:N scheduling model, based on a variant of scheduler activations
. With KSE, a userland process with N threads (1
Scheduler activations had academic backing and the M:N model had proved workable in Solaris, and NetBSD was moving in the same direction, but this decision was made before there was even proof-of-concept code to demonstrate its viability in FreeBSD.
(Ironically, around that time, Sun decided to abandon the M:N model in Solaris, and NetBSD is now moving to 1:1)
To cut a long story short, KSE was a disaster. It took years to implement, delaying other work which depended on it, and it never worked properly. FreeBSD 5 was going nowhere fast until a developer who until then had not been involved in either SMPng or KSE lost patience and implemented a 1:1 thread library on top of KSE. In the end, KSE was never even fully implemented, and it is now being slowly replaced with a pure 1:1 model.
So there you have it. FreeBSD 5 was the result of a failed experiment in M:N threading. FreeBSD 6 was an attempt to correct those mistakes, and FreeBSD 7 will dispose of KSE entirely and complete the fine-grained locking work that started with FreeBSD 5.
Finally, the FreeBSD Project learned an expensive lesson with FreeBSD 5. We now have a separate repository
where experimental code can mature and high-risk changes can be tried out before entering CVS. We have also switched our release model
to time-based releases rather than feature-based releases. If, as a release date approaches, we realize that a particular feature won't be ready in time, we simply leave that feature out of the release rather than change our schedule.